[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18066.59225.533802.387340@cargo.ozlabs.ibm.com>
Date: Tue, 10 Jul 2007 11:56:41 +1000
From: Paul Mackerras <paulus@...ba.org>
To: nigel@...pend2.net
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Matthew Garrett <mjg59@...f.ucam.org>,
Miklos Szeredi <miklos@...redi.hu>,
linux-kernel@...r.kernel.org, Kyle Moffett <mrmacman_g4@....com>,
Pavel Machek <pavel@....cz>,
linux-pm@...ts.linux-foundation.org
Subject: Re: [linux-pm] Re: hibernation/snapshot design [was Re: [PATCH] Remove
process freezer from suspend to RAM pathway]
Nigel Cunningham writes:
> (Finally catching up on emails since Saturday!)
Yes, I know what you mean; I was occupied with other work stuff on
Friday and not well on Saturday, and by that stage there was a backlog
of about 500 emails for me to wade through... :/
> The freezer is also essential for doing a full image of memory - you
> have to be able to guarantee that some of the image won't change in
> order to be able to write it out before the atomic copy. Of course the
> freezer alone isn't enough, but it solves 95% of the issue.
Sure. As I pointed out in another email, it's unrealistic to expect
the freezer to be able to stop everything in a state where any
arbitrary mutex is free. But as long as you don't need to do anything
that depends on getting a mutex while the system is frozen, there
should be no problem.
Paul.
-
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