From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Vivek Goyal <vgoyal@in.ibm.com>,
lguest <lguest@ozlabs.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 0/5] Boot protocol changes
Date: Tue, 02 Oct 2007 16:46:47 -0700 [thread overview]
Message-ID: <4702D867.2060100@goop.org> (raw)
In-Reply-To: <1191368052.17826.40.camel@localhost.localdomain>
Rusty Russell wrote:
> Hi all,
>
> Jeremy had some boot changes for bzImages, but buried in there was an
> update to the boot protocol to support Xen and lguest (and kvm-lite).
> I've copied those fairly simple patches, and if HPA is happy I'd like to
> push them for 2.6.24 (after correcting for the Great Arch Merge of
> course).
Ah, good. I was thinking about reviving this work. The main problem is
that sticking an ELF header at the 1 meg mark (the address of the
bzImage "payload") breaks 32-bit bootloaders which think they can just
jump to 32-bit code there. I started a conversation with Eric at KS
about it, but we didn't reach any conclusions.
This series looks like a good start for Xen, but we still need to work
out where to stash the metadata which normally lives in ELF notes.
Using ELF is convenient for Xen because it lets a large chunk of domain
builder code be reused; on the other hand, loading a plain bzImage is
pretty simple, so maybe it isn't such a big deal.
HPA, Eric: if we don't go the "embed ELF" path, where's a good
backwards-compatible place to stash the note data? If we do go with
"embed ELF", how should we go about doing it? Arrange to put the ELF
headers before the 1M mark?
J
next prev parent reply other threads:[~2007-10-02 23:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 23:34 [PATCH 0/5] Boot protocol changes Rusty Russell
2007-10-02 23:35 ` [PATCH 1/5] update boot spec to 2.07 Rusty Russell
2007-10-02 23:35 ` [PATCH 2/5] add WEAK() for creating weak asm labels Rusty Russell
2007-10-02 23:36 ` [PATCH 3/5] i386: paravirt boot sequence Rusty Russell
2007-10-02 23:39 ` [PATCH 4/5] Revert lguest magic and use hook in head.S Rusty Russell
2007-10-02 23:40 ` [PATCH 5/5] lguest: loading bzImage directly Rusty Russell
2007-10-03 9:37 ` Chris Malley
2007-10-03 17:12 ` H. Peter Anvin
2007-10-04 0:02 ` Rusty Russell
2007-10-04 0:26 ` H. Peter Anvin
2007-11-24 21:54 ` Kjartan Maraas
2007-11-24 22:14 ` H. Peter Anvin
2007-11-25 12:32 ` Kjartan Maraas
2007-10-30 6:38 ` [PATCH 1/5] update boot spec to 2.07 rae l
2007-10-02 23:44 ` [PATCH 0/5] Boot protocol changes H. Peter Anvin
2007-10-02 23:46 ` Jeremy Fitzhardinge [this message]
2007-10-02 23:53 ` H. Peter Anvin
2007-10-02 23:56 ` Jeremy Fitzhardinge
2007-10-03 0:43 ` H. Peter Anvin
2007-10-03 0:46 ` H. Peter Anvin
2007-10-03 0:58 ` Jeremy Fitzhardinge
2007-10-03 1:03 ` H. Peter Anvin
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=4702D867.2060100@goop.org \
--to=jeremy@goop.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=vgoyal@in.ibm.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).