[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1215824537.7319.7.camel@nigel-laptop>
Date: Sat, 12 Jul 2008 11:02:17 +1000
From: Nigel Cunningham <nigel@...el.suspend2.net>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Huang Ying <ying.huang@...el.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
Kexec Mailing List <kexec@...ts.infradead.org>,
Horms <horms@...ge.net.au>
Subject: Re: [PATCH -mm 1/2] kexec jump -v12: kexec jump
Hi.
On Fri, 2008-07-11 at 16:11 -0400, Vivek Goyal wrote:
> Hi Andrew,
>
> We can use this patchset for hibernation, but can it be a better way of doing
> things than what we already have, I don't know. Last time I had raised
> this question and power people had various views. In the end, Pavel wanted
> this patchset to be in. Pavel, can tell more here...
>
> To me this patchset looks interesting for couple of reasons.
>
> - Looks like an interesting feature where one can have a separate kernel
> in memory and one can switch between the kernels on the fly. It can
> be modified to have more than one kernel in memory at a time.
I'm not sure how useful that would be, though. I already have
functionality in TuxOnIce which allows you to resume a different image
instead of powering off (roughly the same thing when combined with not
removing the image after resuming). It was neat when testing to be able
to switch back and forth, and I developed the code because I imagined
that it could form part of the foundation for switching between a login
screen and users' stored sessions. Is this what you're imagining?
> - So far kexec was one directional. One can only kexec to new kernel and
> old kernel was gone. Now this patchset makes kexec functionality kind
> of bidirectional and this looks like logical extension and can lead
> to intersting use cases in future.
Ah. You mean keeping both kernels in memory at the same time? In the
above, I was replacing one image with another.
> Huang also talks of using this feature for snapshotting kernel and
> invoking some BIOS code in protected mode. I am not very sure how exactly
> are they planning to use it. Huang, do you have more details on this?
As Rafael wrote, snapshotting is a completely different beast.
Regards,
Nigel
--
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