[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080312194751.GF13549@redhat.com>
Date: Wed, 12 Mar 2008 15:47:51 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: "Huang, Ying" <ying.huang@...el.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Pavel Machek <pavel@....cz>, nigel@...el.suspend2.net,
"Rafael J. Wysocki" <rjw@...k.pl>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
Kexec Mailing List <kexec@...ts.infradead.org>
Subject: Re: [PATCH -mm] kexec jump -v9
On Wed, Mar 12, 2008 at 09:45:26AM +0800, Huang, Ying wrote:
[..]
> > I have thought through it again and try to put together some of the
> > new kexec options we can introduce to make the whole thing work. I am
> > considering a simple case where a user boots the kernel A and then
> > launches kernel B using "kexec --load-preseve-context". Now a user
> > might save the hibernated image or might want to come back to A.
> >
> > - kexec -l <kernel-image>
> > Normal kexec functionality. Boot a new kernel, without preserving
> > existing kernel's context.
> >
> > - kexec --load-preserve-context <kernel-image>
> > Boot a new kernel while preserving existing kernel's context.
> >
> > Will be used for booting kernel B for the first time.
> >
> > - kexec --load-resume-image <resumable-core>
>
> In original kexec-tools, this can be done through:
> kexec -l --args-none <resumable-core>
>
> Do you need to define an alias for it?
Ok, we can get rid of --load-resume-image and go by the Eric's idea
of detecting image type and taking action accordingly.
Thanks
Vivek
--
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