From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755477AbYDMW06 (ORCPT ); Sun, 13 Apr 2008 18:26:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752400AbYDMW0t (ORCPT ); Sun, 13 Apr 2008 18:26:49 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:37748 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751932AbYDMW0s (ORCPT ); Sun, 13 Apr 2008 18:26:48 -0400 From: "Rafael J. Wysocki" To: benh@kernel.crashing.org Subject: Re: [PATCH 1/3] PM: Introduce new top level suspend and hibernation callbacks (rev. 8) Date: Mon, 14 Apr 2008 00:27:11 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Greg KH , pm list , ACPI Devel Maling List , Alan Stern , Len Brown , LKML , Alexey Starikovskiy , David Brownell , Pavel Machek , Oliver Neukum , Nigel Cunningham , Jesse Barnes , Andrew Morton References: <200804040111.15255.rjw@sisk.pl> <200804132339.45280.rjw@sisk.pl> <1208124646.6958.61.camel@pasglop> In-Reply-To: <1208124646.6958.61.camel@pasglop> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804140027.12161.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, 14 of April 2008, Benjamin Herrenschmidt wrote: > > > > I don't see the point... On the contrary, prepare() is the pefect place > > > to implement handshaking with userspace for drivers that need to do so, > > > such as the DRM. > > > > This _comment_ reflects the current situation, which is that we freeze tasks > > before a suspend. When it's no longer necessary to do that, I'll be happy to > > change this comment. For now, however, that's not the case. > > Can't we run the freezer after prepare() instead ? Well, I'm not sure and I'm not going to introduce the change right now, after the paches have been included in -mm. That would require quite some changes in the core code that I'd prefer to avoid for now. We can do something like this in a separate patch series after the present one settles down a bit. Thanks, Rafael