From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755875AbZBTWpK (ORCPT ); Fri, 20 Feb 2009 17:45:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754074AbZBTWo6 (ORCPT ); Fri, 20 Feb 2009 17:44:58 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:57685 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753060AbZBTWo5 (ORCPT ); Fri, 20 Feb 2009 17:44:57 -0500 From: "Rafael J. Wysocki" To: Oliver Neukum Subject: Re: [RFD] Automatic suspend Date: Fri, 20 Feb 2009 23:44:18 +0100 User-Agent: KMail/1.11.0 (Linux/2.6.29-rc5-tst; KDE/4.2.0; x86_64; ; ) Cc: Alan Stern , Arve =?iso-8859-1?q?Hj=F8nnev=E5g?= , "Woodruff, Richard" , Arjan van de Ven , Kyle Moffett , Benjamin Herrenschmidt , pm list , LKML , Pavel Machek , Nigel Cunningham , Matthew Garrett , mark gross , Uli Luckas , Igor Stoppa , Brian Swetland , Len Brown References: <200902201146.59944.rjw@sisk.pl> <200902202305.09992.oliver@neukum.org> In-Reply-To: <200902202305.09992.oliver@neukum.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902202344.20040.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 20 February 2009, Oliver Neukum wrote: > Am Freitag 20 Februar 2009 11:46:55 schrieb Rafael J. Wysocki: > > On Thursday 19 February 2009, Oliver Neukum wrote: > > > Am Donnerstag 19 Februar 2009 23:21:46 schrieb Rafael J. Wysocki: > > > > > That's the whole point behind userspace wakelocks! They provide a > > > > > mechanism for userspace to tell the kernel when (as far as userspace > > > > > > is > > > > > > > > concerned) it is or is not okay to auto-sleep. > > > > > > > > Still, one can go further and observe that the user space can in fact > > > > start automatic suspend by itself whenever it knows it's appropriate > > > > ... > > > > > > User space initiating this is a race condition. > > > > Do you mean a race with the other user space processes or with the kernel? > > With the set of runnable processes.There's always a window between > evaluating the current set of runnable tasks and telling the kernel to sleep. > IMO the most elegant solution would be a task attribute that would signal > the kernel that a task should not count as keeping the system busy even > if it is runnable and trigger the sleep in kernel space. Please see my last reply to Arve (http://lkml.org/lkml/2009/2/20/182) and tell me what you think. Best, Rafael