From: Vivek Goyal <vgoyal@redhat.com>
To: Scot Doyle <lkml14@scotdoyle.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Kexec Mailing List <kexec@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Andi Kleen <andi@firstfloor.org>, Borislav Petkov <bp@alien8.de>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Dave Young <dyoung@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: Edited kexec_load(2) [kexec_file_load()] man page for review
Date: Wed, 28 Jan 2015 16:31:25 -0500 [thread overview]
Message-ID: <20150128213125.GH15342@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1501282104490.9275@localhost.localdomain>
On Wed, Jan 28, 2015 at 09:14:03PM +0000, Scot Doyle wrote:
> On Wed, 28 Jan 2015, Vivek Goyal wrote:
> > On Wed, Jan 28, 2015 at 04:49:34PM +0100, Michael Kerrisk (man-pages) wrote:
> > > Hello Vivek,
> > >
> > > >> I've made various adjustments to the page in the light of your comments
> > > >> above. Thanks!
> > > >
> > > > Thank you for following it up and improving kexec man page.
> > >
> > > You're welcome. So, by now, I've made quite a lot of changes
> > > (including adding a number of cases under ERRORS). I think the revised
> > > kexec_load/kexec_file_load page is pretty much ready to go, but would
> > > you be willing to give the text below a check over first?
> > >
> >
> > Hi Michael,
> >
> > I had a quick look and it looks good to me.
> >
> > Thanks
> > Vivek
>
> When I tested, kexec_file_load required CONFIG_RELOCATABLE. Is the same
> true for kexec_load? Would it make sense to note this in the man pages
> along with the need for CONFIG_KEXEC_FILE, etc? Or as an error message?
Hmm.., I can't see an explicity dependency between RELOCATABLE and
KEXEC. Both KEXEC and KEXEC_FILE should be able to load a kernel
even if it had RELOCATABLE=n.
Just that kernel will run from the address it has been built for.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-01-28 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 19:17 Edited kexec_load(2) [kexec_file_load()] man page for review Michael Kerrisk (man-pages)
2014-11-11 21:30 ` Vivek Goyal
2015-01-07 21:17 ` Michael Kerrisk (man-pages)
2015-01-12 22:16 ` Vivek Goyal
2015-01-16 13:30 ` Michael Kerrisk (man-pages)
2015-01-27 8:07 ` Michael Kerrisk (man-pages)
2015-01-27 14:24 ` Vivek Goyal
2015-01-28 8:04 ` Michael Kerrisk (man-pages)
2015-01-28 14:48 ` Vivek Goyal
2015-01-28 15:49 ` Michael Kerrisk (man-pages)
2015-01-28 20:34 ` Vivek Goyal
2015-01-28 21:14 ` Scot Doyle
2015-01-28 21:31 ` Vivek Goyal [this message]
2015-01-28 22:10 ` Scot Doyle
2015-01-28 22:25 ` Vivek Goyal
2015-01-29 1:27 ` Scot Doyle
2015-01-29 5:39 ` Michael Kerrisk (man-pages)
2015-01-29 16:06 ` Scot Doyle
2015-01-30 15:25 ` Michael Kerrisk (man-pages)
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=20150128213125.GH15342@redhat.com \
--to=vgoyal@redhat.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=lkml14@scotdoyle.com \
--cc=luto@amacapital.net \
--cc=mtk.manpages@gmail.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;
as well as URLs for NNTP newsgroup(s).