From: Pavel Machek <pavel@ucw.cz>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
nigel@nigel.suspend2.net, "Rafael J. Wysocki" <rjw@sisk.pl>,
Jeremy Maitin-Shepard <jbms@cmu.edu>,
Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
david@lang.hm, linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATH 1/1] Kexec jump - v2 - kexec jump
Date: Tue, 31 Jul 2007 11:51:01 +0200 [thread overview]
Message-ID: <20070731095101.GA1774@elf.ucw.cz> (raw)
In-Reply-To: <1184483639.1898.99.camel@caritas-dev.intel.com>
Hi!
> This patch implement the functionality of jumping from kexeced kernel
> to original kernel.
>
> A new reboot command named LINUX_REBOOT_CMD_KJUMP is defined to
> trigger the jumping to (executing) the new kernel or jumping back to
> the original kernel.
Could we get two reboot commands? Exec loaded kernel seems to be quite
different operation than "jump back".
How do I test these patches? kexec -p <bzImage>, then kexec -j?
> +static unsigned long kexec_backup_addr = ~0UL;
> +
> +/* kexec_backup= specifies the location of backuped 0~640k memory of
> + * crashed kernel.
> + */
> +static int __init parse_kexec_backup(char *arg)
> +{
> + if (!arg)
> + return -EINVAL;
> +
> + kexec_backup_addr = memparse(arg, &arg);
> + return 0;
> +}
> +early_param("kexec_backup", parse_kexec_backup);
New kernel parameters should be documented. (Plus I do not know how to
use this one, please help :-).
> +int kexec_flags;
> +
> +static unsigned long kexec_jump_buf_pfn;
> +
> +static int __init parse_kexec_jump_buf_pfn(char *arg)
> +{
> + if (!arg)
> + return -EINVAL;
> +
> + kexec_jump_buf_pfn = memparse(arg, &arg);
> + kexec_flags |= KEXEC_FLAGS_IS_KEXECED_KERNEL;
> + return 0;
> +}
> +early_param("kexec_jump_buf_pfn", parse_kexec_jump_buf_pfn);
This one should be documented, too, I'd guess. (Is that internal,
kernel-to-kernel communication?)
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:[~2007-07-31 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 7:13 [PATH 1/1] Kexec jump - v2 - kexec jump Huang, Ying
2007-07-31 9:51 ` Pavel Machek [this message]
2007-08-01 7:56 ` Huang, Ying
2007-08-05 18:50 ` Pavel Machek
2007-08-16 10:26 ` [linux-pm] " Pavel Machek
2007-08-17 6:15 ` Huang, Ying
2007-08-21 10:14 ` Pavel Machek
2007-08-22 6:51 ` 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=20070731095101.GA1774@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=david@lang.hm \
--cc=ebiederm@xmission.com \
--cc=jbms@cmu.edu \
--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=stern@rowland.harvard.edu \
--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