lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190207152908.GC14464@e107155-lin>
Date:   Thu, 7 Feb 2019 15:29:08 +0000
From:   Sudeep Holla <sudeep.holla@....com>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Jisheng Zhang <jszhang@...vell.com>,
        Steve Longerbeam <slongerbeam@...il.com>,
        Eugeniu Rosca <erosca@...adit-jv.com>,
        Joshua Frkuska <joshua_frkuska@...tor.com>,
        Eugeniu Rosca <roscaeugeniu@...il.com>,
        Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH] drivers: base: add support to skip power management in
 device/driver model

On Thu, Feb 07, 2019 at 04:18:57PM +0100, Ulf Hansson wrote:
> On Thu, 7 Feb 2019 at 16:06, Sudeep Holla <sudeep.holla@....com> wrote:

[...]

> > Indeed, I was ignoring knowing that it's harmless. But more people
> > started to complain, and Rafael suggested this which I agree as we
> > have several pseudo devices created in the kernel that we can bypass
> > some of these pm handling knowing we won't need it.
>
> Okay, I see.
>
> Anyway, I will likely need to restore part of this change, via my
> cluster idling series then. As from that point, the cpu device that
> you call device_set_pm_not_required() for, starts to be used from both
> PM core and runtime PM point of view. But I guess that's okay then.
>

Ah I see. I can drop for CPU devices then. Since I didn't see any use for
them, I set the flag, but I can drop it now or you can do that as part
of that series. There are quite a few devices(especially the ones
registered under system subsys can set this but I would take it separate
once we settle on this). Also Rafael may have seen use for few more
devices when he suggested this.

--
Regards,
Sudeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ