linux-kernel - [RFC] Plan to get rid of all legacy PM handling

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-next>] [day] [month] [year] [list]

Date:	Sun, 17 Jun 2012 23:10:49 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Linux PM list <linux-pm@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: [RFC] Plan to get rid of all legacy PM handling

Hi all,

I have a plan to replace all of the legacy device PM callbacks throughout
the kernel with PM handling based on struct dev_pm_ops objects.  Ultimately,
that should make it possible to remove the legacy hooks from struct bus_type
and struct device_driver and to siplify the PM core and some bus types
(most importantly PCI) quite a bit.

I'm going to start with platform drivers that should be the most
straightforward to convert and when they all have been dealt with it
should be possible to drop the platform bus type's PM callbacks entirely.
Next, I'm going to take care of the bus types that only define PM callbacks
to call drivers' callbacks, which is completely unnecessary after some PM
core changes that went in during the 3.4 development cycle.  Finally, I will
be looking at PCI drivers.

The task is huge, but I've done similar things already, so it's nothing new
to me.  So, if you're a maintainer of code that contains legacy PM handling,
please be prepared to see some patches from me in a not-too-distant-future.

Thanks,
Rafael
--
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/