Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933695Ab0FEQ00 (ORCPT ); Sat, 5 Jun 2010 12:26:26 -0400 Received: from casper.infradead.org ([85.118.1.10]:45791 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933645Ab0FEQ0Z convert rfc822-to-8bit (ORCPT ); Sat, 5 Jun 2010 12:26:25 -0400 Date: Sat, 5 Jun 2010 09:28:51 -0700 From: Arjan van de Ven To: Peter Zijlstra Cc: Arve =?UTF-8?B?SGrDuG5uZXbDpWc=?= , Ingo Molnar , tytso@mit.edu, Brian Swetland , Neil Brown , Thomas Gleixner , "Rafael J. Wysocki" , Alan Stern , Felipe Balbi , LKML , Florian Mickler , Linux OMAP Mailing List , Linux PM , Alan Cox , James Bottomley , Linus Torvalds , Kevin Hilman , "H. Peter Anvin" Subject: Re: suspend blockers & Android integration Message-ID: <20100605092851.6ee15f13@infradead.org> In-Reply-To: <1275731653.27810.41078.camel@twins> References: <20100603193045.GA7188@elte.hu> <20100603231153.GA11302@elte.hu> <20100603232302.GA16184@elte.hu> <20100604071354.GA14451@elte.hu> <20100604083423.GD15181@elte.hu> <1275653210.27810.39762.camel@twins> <1275731653.27810.41078.camel@twins> Organization: Intel X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1385 Lines: 36 On Sat, 05 Jun 2010 11:54:13 +0200 Peter Zijlstra 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/