On Sat, 05 Jun 2010 11:54:13 +0200 Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > On Fri, 2010-06-04 at 17:10 -0700, Arve Hjønnevåg wrote: > > > Trusted processes are assumed to be sane and idle when there is > > > nothing for them to do, allowing the machine to go into deep idle > > > states. > > > > > > > Neither the kernel nor our trusted user-space code currently meets > > this criteria. > > Then both need fixing. Really, that's the only sane approach. fwiw... in MeeGo we're seeing quite good idle times (> 1 seconds) without really bad hacks. the kernel has a set of infrastructure already to help here (range timers, with which you can wakeup-limit untrusted userspace crap), timer slack for legacy background timers, etc etc. getting to 10 seconds is not in the range of impossibilities to be honest... and that's even without doing things like putting untrusted junk (read: Appstore apps) into a cgroup and do wakeup limiting and cpu time limiting on a cgroup level.... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm