From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Re: [PATCH] Remove process freezer from suspend to RAM pathway Date: Tue, 03 Jul 2007 21:40:26 +1000 Message-ID: <1183462826.10386.107.camel@localhost.localdomain> References: <20070703042916.GA17240@srcf.ucam.org> <200707031608.06348.nigel@nigel.suspend2.net> <1183447184.10386.102.camel@localhost.localdomain> <200707030944.18702.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200707030944.18702.oliver@neukum.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Oliver Neukum Cc: Matthew Garrett , linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org List-Id: linux-pm@vger.kernel.org On Tue, 2007-07-03 at 09:44 +0200, Oliver Neukum wrote: > Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt: > > So to summarize, the plan that makes things work with fuse is: > > > > - For STR, don't do the freezer thing. > > > > - For STD, don't sys_sync() after you froze > > > > There might be -other- issues, but that should get you through some of > > At the risk of repeating myself. Character device drivers are written > with the assumption that normal io and suspend/resume do not race > with each other due to the freezer. > What do you intend to do about that? Ugh ... "character devices" ... that's a pretty wide statement... there's lots of those and very different one from the other... Any sane device-driver will have to cope with being suspended in a "live" system. I've demonstrated multiple times in the past why this is necessary anyway, for things like dynamic power management, among others. The whole freezer thing is a hack job to avoid fixing drivers that need fixing. Unfortunately, I believe in that area, it's simply not sustainable. Besides, getting drivers to behave properly isn't very hard in most cases. Ben.