From: Pavel Machek <pavel@suse.cz>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>,
Andrew Morton <akpm@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"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, 4 Aug 2008 13:01:00 +0200 [thread overview]
Message-ID: <20080804110100.GF12341@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20080714133221.GC16673@redhat.com>
> On Mon, Jul 14, 2008 at 07:46:44AM +0200, Pavel Machek wrote:
> > On Sat 2008-07-12 11:02:17, 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
> >
> > Beaty of kjump is that it is supposed to used on half-broken system,
> > so it is useful for debugging.
> >
>
> What do you mean by supposed to be used on half-broken system?
Maybe some network driver went wrong (but rest of machine keeps
working), so you want to do kdump but do not want to kill the machine
(as the remaining network drivers make the server useful).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-08-04 11:01 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
2008-07-14 5:46 ` Pavel Machek
2008-07-14 13:32 ` Vivek Goyal
2008-08-04 11:01 ` Pavel Machek [this message]
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=20080804110100.GF12341@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--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=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®