From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932797Ab0EMVzI (ORCPT ); Thu, 13 May 2010 17:55:08 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:54652 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932357Ab0EMVzC (ORCPT ); Thu, 13 May 2010 17:55:02 -0400 From: "Rafael J. Wysocki" To: Tony Lindgren Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6) Date: Thu, 13 May 2010 23:56:21 +0200 User-Agent: KMail/1.12.4 (Linux/2.6.34-rc7-rjw; KDE/4.3.5; x86_64; ; ) Cc: Matthew Garrett , Alan Stern , Paul Walmsley , Arve =?iso-8859-1?q?Hj=F8nnev=E5g?= , "Linux-pm mailing list" , Kernel development list , Tejun Heo , Oleg Nesterov , Kevin Hilman , magnus.damm@gmail.com, "Theodore Ts'o" , mark gross , Arjan van de Ven , Geoff Smith , Brian Swetland , =?iso-8859-1?q?Beno=EEt_Cousson?= , linux-omap@vger.kernel.org, Vitaly Wool , Mark Brown , Liam Girdwood References: <201005132321.59245.rjw@sisk.pl> <20100513212556.GI3428@atomide.com> In-Reply-To: <20100513212556.GI3428@atomide.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005132356.21355.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 13 May 2010, Tony Lindgren wrote: > * Rafael J. Wysocki [100513 14:16]: > > On Thursday 13 May 2010, Matthew Garrett wrote: > > > On Thu, May 13, 2010 at 01:23:20PM -0700, Tony Lindgren wrote: > > > > * Matthew Garrett [100513 13:03]: > > > > > On Thu, May 13, 2010 at 01:00:04PM -0700, Tony Lindgren wrote: > > > > > > > > > > > The system stays running because there's something to do. The system > > > > > > won't suspend until all the processors hit the kernel idle loop and > > > > > > the next_timer_interrupt_critical() returns nothing. > > > > > > > > > > At which point an application in a busy loop cripples you. > > > > > > > > Maybe you could deal with the misbehaving untrusted apps in the userspace > > > > by sending kill -STOP to them when the screen blanks? Then continue > > > > when some event wakes up the system again. > > > > > > And if that's the application that's listening to the network socket > > > that you want to get a wakeup event from? This problem is hard. I'd love > > > there to be an elegant solution based on using the scheduler, but I > > > really don't know what it is. > > > > I agree and I don't understand the problem that people have with the > > opportunistic suspend feature. > > It seems to be picking quite a few comments for one. > > > It solves a practical issue that _at_ _the_ _moment_ cannot be solved > > differently, while there's a growing number of out-of-tree drivers depending > > on this framework. We need those drivers in and because we don't have any > > viable alternative at hand, we have no good reason to reject it. > > Nothing is preventing merging the drivers can be merged without > these calls. And yet, there _is_ a growing nuber of drivers that don't get merge because of that. That's _reality_. Are you going to discuss with facts, or what? Rafael