[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0707171535350.2467@asgard.lang.hm>
Date: Tue, 17 Jul 2007 15:37:07 -0700 (PDT)
From: david@...g.hm
To: Alan Stern <stern@...land.harvard.edu>
cc: "Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Huang, Ying" <ying.huang@...el.com>,
Jeremy Maitin-Shepard <jbms@....edu>,
Kyle Moffett <mrmacman_g4@....com>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Pavel Machek <pavel@....cz>,
pm list <linux-pm@...ts.linux-foundation.org>,
Al Boldi <a1426z@...ab.com>
Subject: Re: Hibernation considerations
On Tue, 17 Jul 2007, Alan Stern wrote:
> On Tue, 17 Jul 2007 david@...g.hm wrote:
>
>>> But what about the freezer? The original reason for using kexec was to
>>> avoid the need for the freezer. With no freezer, while the original
>>> kernel is busy powering down its devices, user tasks will be free to
>>> carry out I/O -- which will make the memory snapshot inconsistent with
>>> the on-disk data structures.
>>
>> no, user tasks just don't get scheduled during shutdown.
>
> But a user task may be holding a lock which is needed for putting some
> device into low-power mode. It can't release that lock if it doesn't
> get scheduled.
then you can't suspend that box. if you schedule it, it could get another
lock (or another process gets another lock)
if you can't power down or put hardware into low-power mode without the
approval of userspace, you are in serious trouble.
David Lang
-
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