From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) Date: Thu, 27 May 2010 19:29:13 +0100 Message-ID: <20100527182913.GO3543@srcf.ucam.org> References: <1274982779.27810.5708.camel@twins> <20100527175719.GD3543@srcf.ucam.org> <1274983333.27810.5744.camel@twins> <20100527181433.GG3543@srcf.ucam.org> <1274984291.27810.5802.camel@twins> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:42855 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934486Ab0E0S3a (ORCPT ); Thu, 27 May 2010 14:29:30 -0400 Content-Disposition: inline In-Reply-To: <1274984291.27810.5802.camel@twins> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Peter Zijlstra Cc: Alan Stern , Thomas Gleixner , Paul@smtp1.linux-foundation.org, LKML , Florian Mickler , felipe.balbi@nokia.com, Linux OMAP Mailing List , Linux PM , Alan Cox On Thu, May 27, 2010 at 08:18:11PM +0200, Peter Zijlstra wrote: > On Thu, 2010-05-27 at 19:14 +0100, Matthew Garrett wrote: > > If I get a WoL > > packet in the 0.5 of a second between userspace deciding to suspend and > > actually doing so, the system shouldn't suspend. > > Please re-read Thomas' description of how a driver should do the state > transition. > > So either we get the packet before suspend, and we cancel the suspend, > or we get it after and we wake up. What's the problem, and how does that > need suspend blockers? In order to cancel the suspend we need to keep track of whether userspace has consumed the event and reacted appropriately. Since we can't do this with the process scheduler, we end up with something that looks like suspend blockers. -- Matthew Garrett | mjg59@srcf.ucam.org