From: Pavel Machek <pavel@ucw.cz>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: david@lang.hm, nigel@nigel.suspend2.net,
Kexec Mailing List <kexec@lists.infradead.org>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pm@lists.linux-foundation.org,
Jeremy Maitin-Shepard <jbms@cmu.edu>
Subject: Re: [linux-pm] Re: [PATH 1/1] Kexec jump - v2 - kexec jump
Date: Thu, 16 Aug 2007 12:26:35 +0200 [thread overview]
Message-ID: <20070816102635.GA2039@elf.ucw.cz> (raw)
In-Reply-To: <1185954978.1363.23.camel@caritas-dev.intel.com>
Hi!
> > > +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?)
>
> Document will be added in next version too.
Ping... is there some next version?
I'm stuck at the tools side currently. kexec-1.101 just won't load the
kernel properly, and kexec-testing from git does not know -j option. I
tried hand-patching it, but got lots of scary rejects.
Is there chance for a patch against kexec-testing?
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-08-16 13:08 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
2007-08-01 7:56 ` Huang, Ying
2007-08-05 18:50 ` Pavel Machek
2007-08-16 10:26 ` Pavel Machek [this message]
2007-08-17 6:15 ` [linux-pm] " 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=20070816102635.GA2039@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=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