linux-kernel - Re: [PATCH 0/4] PM: Use CONFIG_PM instead of CONFIG_PM

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Nov 2014 17:52:46 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Ulf Hansson <ulf.hansson@...aro.org>
Cc:	Linux PM list <linux-pm@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Kevin Hilman <khilman@...nel.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH 0/4] PM: Use CONFIG_PM instead of CONFIG_PM_RUNTIME in core code

On Thursday, November 27, 2014 09:57:33 AM Ulf Hansson wrote:
> On 27 November 2014 at 01:37, Rafael J. Wysocki <rjw@...ysocki.net> wrote:
> > Hi,
> >
> > After commit b2b49ccbdd54 "PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
> > selected" (currently in Linux next) CONFIG_PM_RUNTIME is set whenever
> > CONFIG_PM is set, so CONFIG_PM can be used in #ifdefs instead of
> > CONFIG_PM_RUNTIME which simplifies things in quite a few cases.
> >
> > For this reason, the following patches modify some core code to use
> > CONFIG_PM instead of CONFIG_PM_RUNTIME.
> >
> > [1/4] Drop a macro which is redundant after the above commit.
> > [2/4] Use PM instead of PM_RUNTIME in the core device PM code.
> > [3/4] Use PM instead of PM_RUNTIME in the ACPI core.
> > [4/4] Use PM instead of PM_RUNTIME in the PCI core.
> >
> > They build for me for all of the relevant combinations of options (on x86),
> > but more testing (on the other architectures) would be welcome.
> 
> I really like the looks of this patchset!
> 
> Noticed that you have applied it for your bleeding edge branch, I
> suppose that means you will get some "free" testing in linux-next?
> 
> Anyway, I have tested it for ux500 (including the genpd support for
> it, available in linux-next). It works nicely!
> 
> I have also tested the two Kconfig options; CONFIG_PM_SLEEP (which
> selects CONFIG_PM_RUNTIME) and for CONFIG_PM_RUNTIME (with
> CONFIG_PM_SLEEP unset).
> 
> That brings me to a raise a question; why do we need to keep these two
> configurations options? Couldn't we also have CONFIG_PM_RUNTIME to
> select CONFIG_PM_SLEEP, that will further simplify things?

My plan is different.  I'm going to eliminate PM_RUNTIME from the code
and then replace it with PM as a selectable option.  Then, PM_SLEEP will
select PM (directly) and PM_RUNTIME can be entirely dropped.

So in the end we'll have one Kconfig option less, which is a win IMO.

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/