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
| ||
|
Date: Mon, 16 Feb 2009 08:02:32 +0100 From: Oliver Neukum <oliver@...kum.org> To: Arjan van de Ven <arjan@...radead.org> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, pm list <linux-pm@...ts.linux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, Arve Hjønnevåg <arve@...roid.com>, Alan Stern <stern@...land.harvard.edu>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Pavel Machek <pavel@....cz>, Nigel Cunningham <nigel@...el.suspend2.net>, Matthew Garrett <mjg59@...f.ucam.org>, mark gross <mgross@...ux.intel.com>, "Woodruff, Richard" <r-woodruff2@...com>, Uli Luckas <u.luckas@...d.de>, Igor Stoppa <igor.stoppa@...ia.com>, Brian Swetland <swetland@...gle.com>, Len Brown <lenb@...nel.org> Subject: Re: [RFD] Automatic suspend Am Monday 16 February 2009 01:44:56 schrieb Arjan van de Ven: > On Mon, 16 Feb 2009 00:10:15 +0100 > "Rafael J. Wysocki" <rjw@...k.pl> wrote: > > > Hi, > > > > The recent descussion about the Android PM patches sent by Arve shows > > that there is a need to introduce a mechanism allowing us to: > > (1) automatically put the system as a whole into a sleep state (eg. > > suspend to RAM) when it is found to be "idle", where the meaning of > > "idle" has to be defined too, > > (2) put given subset of devices into low power states whenever they > > are not used, without putting the entire system into a sleep state. > > > For (2), for me the answer is very obvious: > > The Device Driver needs to make the decision to put the device to sleep. > There are no ifs and buts about this. > > It's the driver who > a) knows if there's any activity, such as open users > and > b) is in the right position to know how to put things to sleep. I think you need third option between decides to put to sleep and refuses to put to sleep. It is probably necessary to let drivers state that they would want to go along if the whole system goes to sleep. > Of course, the subsystem the driver belongs to can provide helpers > (such as generic activity timeout handlers etc). > > For many cases, the drivers do this today already. > There are cases where doing this has side effects, mostly in terms of > latency. It is reasonable to have a general mechanism that provides a Exactly. Regards Oliver -- 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/
Powered by blists - more mailing lists