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

On Sat, Jul 12, 2008 at 11:02:17AM +1000, Nigel Cunningham wrote:
> 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?
> 

I did not think of that. I thought of two things.

- This can possibly be used for non-disruptive kernel crash dumping, where
  if a user wants to capture the snapshot of kernel and then continue
  to work. Thought, it might be little heavy weight solution and kernel
  state also has changed a bit by the time dump is captured (because of
  all the suspend code).

- One can have two distributions installed on a single system and switch
  between two booted kernels in few seconds.

> > - 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.

Yes, here both the kernels will remain in the RAM. In fact it should be
easily possible to keep more than 2 kernels in memory and switch between
these.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
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: Mon, 14 Jul 2008 09:09:55 -0400	[thread overview]
Message-ID: <20080714130955.GA16673@redhat.com> (raw)
In-Reply-To: <1215824537.7319.7.camel@nigel-laptop>

On Sat, Jul 12, 2008 at 11:02:17AM +1000, Nigel Cunningham wrote:
> 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?
> 

I did not think of that. I thought of two things.

- This can possibly be used for non-disruptive kernel crash dumping, where
  if a user wants to capture the snapshot of kernel and then continue
  to work. Thought, it might be little heavy weight solution and kernel
  state also has changed a bit by the time dump is captured (because of
  all the suspend code).

- One can have two distributions installed on a single system and switch
  between two booted kernels in few seconds.

> > - 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.

Yes, here both the kernels will remain in the RAM. In fact it should be
easily possible to keep more than 2 kernels in memory and switch between
these.

Thanks
Vivek

  parent reply	other threads:[~2008-07-14 13:09 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07  3:25 [PATCH -mm 1/2] kexec jump -v12: kexec jump Huang Ying
2008-07-07  3:25 ` Huang Ying
2008-07-07 12:50 ` Pavel Machek
2008-07-07 12:50   ` Pavel Machek
2008-07-08  9:10   ` Huang Ying
2008-07-08  9:10   ` Huang Ying
2008-07-08  9:10     ` Huang Ying
2008-07-08 10:40     ` Pavel Machek
2008-07-08 10:40     ` Pavel Machek
2008-07-08 10:40       ` Pavel Machek
2008-07-09  1:12       ` Huang Ying
2008-07-09  1:12         ` Huang Ying
2008-07-09  1:12       ` Huang Ying
2008-07-07 12:50 ` Pavel Machek
2008-07-08 14:50 ` Vivek Goyal
2008-07-08 14:50 ` Vivek Goyal
2008-07-08 14:50   ` Vivek Goyal
2008-07-09  1:09   ` Huang Ying
2008-07-09  1:09   ` Huang Ying
2008-07-09  1:09     ` Huang Ying
2008-07-11 19:21   ` Andrew Morton
2008-07-11 19:21     ` Andrew Morton
2008-07-11 20:11     ` Vivek Goyal
2008-07-11 20:11       ` Vivek Goyal
2008-07-12  1:02       ` Nigel Cunningham
2008-07-12  1:02         ` Nigel Cunningham
2008-07-14  5:46         ` Pavel Machek
2008-07-14  5:46         ` Pavel Machek
2008-07-14  5:46           ` Pavel Machek
2008-07-14 13:32           ` Vivek Goyal
2008-07-14 13:32           ` Vivek Goyal
2008-07-14 13:32             ` Vivek Goyal
2008-08-04 11:01             ` Pavel Machek
2008-08-04 11:01               ` Pavel Machek
2008-08-04 11:01             ` Pavel Machek
2008-07-14 13:09         ` Vivek Goyal [this message]
2008-07-14 13:09           ` Vivek Goyal
2008-07-14 13:09         ` Vivek Goyal
2008-07-12  1:02       ` Nigel Cunningham
2008-07-11 20:11     ` Vivek Goyal
2008-07-11 20:24     ` Pavel Machek
2008-07-11 20:24     ` Pavel Machek
2008-07-11 20:24       ` Pavel Machek
2008-07-11 20:40       ` Rafael J. Wysocki
2008-07-11 20:40       ` Rafael J. Wysocki
2008-07-11 20:40         ` Rafael J. Wysocki
2008-07-12  2:23         ` Eric W. Biederman
2008-07-12  2:23         ` Eric W. Biederman
2008-07-12  2:23           ` Eric W. Biederman
2008-07-12  3:04           ` [linux-pm] " Alan Stern
2008-07-12  3:04             ` Alan Stern
2008-07-12  3:50             ` Eric W. Biederman
2008-07-12  3:50               ` Eric W. Biederman
2008-07-12 18:52               ` Rafael J. Wysocki
2008-07-12 18:52                 ` Rafael J. Wysocki
2008-07-12 18:52               ` Rafael J. Wysocki
2008-07-12 19:55               ` Alan Stern
2008-07-12 19:55               ` [linux-pm] " Alan Stern
2008-07-12 19:55                 ` Alan Stern
2008-07-12  3:50             ` Eric W. Biederman
2008-07-12  3:04           ` Alan Stern
2008-07-14 13:30     ` huang ying
2008-07-14 13:30     ` huang ying
2008-07-14 13:30       ` huang ying
2008-07-14 13:30     ` huang ying
2008-07-11 19:21   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2008-07-07  3:25 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=20080714130955.GA16673@redhat.com \
    --to=vgoyal@redhat.com \
    --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=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.