From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755338AbXGHFTc (ORCPT ); Sun, 8 Jul 2007 01:19:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751667AbXGHFT0 (ORCPT ); Sun, 8 Jul 2007 01:19:26 -0400 Received: from gate.crashing.org ([63.228.1.57]:45193 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522AbXGHFTZ (ORCPT ); Sun, 8 Jul 2007 01:19:25 -0400 Subject: Re: [PATCH] Remove process freezer from suspend to RAM pathway From: Benjamin Herrenschmidt To: Alan Stern Cc: Kyle Moffett , Nigel Cunningham , Pavel Machek , "Rafael J. Wysocki" , Matthew Garrett , linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org In-Reply-To: <1183871661.3388.282.camel@localhost.localdomain> References: <1183871661.3388.282.camel@localhost.localdomain> Content-Type: text/plain Date: Sun, 08 Jul 2007 15:19:01 +1000 Message-Id: <1183871941.3388.286.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > I think it's a fairly significant change from the current freezer and I > also think it's a very good idea. The more I think about it, the more I > like it, in the sense that it's a simple drop-in that you could put in a > lot of the ioctl path of drivers to just block tasks that are trying to > call in while suspending, and could be used selectively by things like > the USB hub threads. Note that we could have also a per-device "icebox" (just a waitqueue). Might be nice for a device to resume whatever it froze just after it resumed itself, might even be necessary in case whatever thread got frozen is necessary for handling child devices. Cheers, Ben.