[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zm1qofnr.fsf@jbms.ath.cx>
Date: Fri, 20 Jul 2007 18:48:24 -0400
From: Jeremy Maitin-Shepard <jbms@....edu>
To: Alan Stern <stern@...land.harvard.edu>
Cc: david@...g.hm, Milton Miller <miltonm@....com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Ying Huang <ying.huang@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-pm <linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] Re: Hibernation considerations
Alan Stern <stern@...land.harvard.edu> writes:
> On Fri, 20 Jul 2007, Jeremy Maitin-Shepard wrote:
>> >> when doing a suspend-to-ram you get to a point where you just don't use
>> >> any userspace.
>>
>> > What do you mean? How can you prevent user tasks from running? That's
>> > basically what the freezer does, and the whole point of this approach
>> > is to eliminate the freezer. Right?
>>
>> Presumably no tasks at all would be scheduled.
> How would you prevent tasks from being scheduled? How would you
> prevent drivers from deadlocking because in order to put their device
> in a low-power state they need to acquire a lock which is held by a
> user task?
Perhaps this isn't an issue once the device is already quiesced. I'm
just conjecturing.
[snip]
--
Jeremy Maitin-Shepard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists