mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Huang Ying <ying.huang@intel.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org,
	Kexec Mailing List <kexec@lists.infradead.org>,
	Horms <horms@verge.net.au>
Subject: Re: [PATCH -mm 1/2] kexec jump -v12: kexec jump
Date: Sat, 12 Jul 2008 11:02:17 +1000	[thread overview]
Message-ID: <1215824537.7319.7.camel@nigel-laptop> (raw)
In-Reply-To: <20080711201149.GB3298@redhat.com>

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


  reply	other threads:[~2008-07-12  1:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07  3:25 Huang Ying
2008-07-07 12:50 ` Pavel Machek
2008-07-08  9:10   ` Huang Ying
2008-07-08 10:40     ` Pavel Machek
2008-07-09  1:12       ` Huang Ying
2008-07-08 14:50 ` Vivek Goyal
2008-07-09  1:09   ` Huang Ying
2008-07-11 19:21   ` Andrew Morton
2008-07-11 20:11     ` Vivek Goyal
2008-07-12  1:02       ` Nigel Cunningham [this message]
2008-07-14  5:46         ` Pavel Machek
2008-07-14 13:32           ` Vivek Goyal
2008-08-04 11:01             ` Pavel Machek
2008-07-14 13:09         ` Vivek Goyal
2008-07-11 20:24     ` Pavel Machek
2008-07-11 20:40       ` Rafael J. Wysocki
2008-07-12  2:23         ` Eric W. Biederman
2008-07-12  3:04           ` [linux-pm] " Alan Stern
2008-07-12  3:50             ` Eric W. Biederman
2008-07-12 18:52               ` Rafael J. Wysocki
2008-07-12 19:55               ` Alan Stern
2008-07-14 13:30     ` huang ying

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1215824537.7319.7.camel@nigel-laptop \
    --to=nigel@nigel.suspend2.net \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=vgoyal@redhat.com \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®