From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Vivek Goyal <vgoyal@in.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [patch rfc wip] first cut of ELF bzImage
Date: Thu, 31 May 2007 00:43:30 -0700 [thread overview]
Message-ID: <465E7CA2.6090201@zytor.com> (raw)
In-Reply-To: <465E78D2.9080609@goop.org>
The more I'm thinking about this whole issue, the more I'm thinking this
is really misdirected.
I'm starting to think that the right thing to do might very well be as
follows:
- Change the payload of the bzImage file from a flat binary to an ELF
file -- a stripped vmlinux.gz.
- Change the decompressor to incorporate a (simple) ELF parser.
- Incorporate a couple of pointer fields in the bzImage header that
points directly to the payload, the format of which can be identified
via its magic number (currently gzip).
That way the environments that want to enter at the protected-mode
entrypoint can do their own setup using whatever information is retained
in the payload. Since most of these environments are currently using
vmlinux as their boot file, this seems to make sense.
The more I hear about copying notes and various things from vmlinux to
bzImage the more I'm convinced that this is a huge kluge. Furthermore,
there are *definitely* virtual environments which would be much happier
to be able to decompress in host space. The decompressor doesn't run
well in many simulators.
-hpa
next prev parent reply other threads:[~2007-05-31 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 7:27 [patch rfc wip] first cut of ELF bzImage Jeremy Fitzhardinge
2007-05-31 7:43 ` H. Peter Anvin [this message]
2007-05-31 7:52 ` Jeremy Fitzhardinge
2007-05-31 8:12 ` Rusty Russell
2007-05-31 17:52 ` H. Peter Anvin
2007-05-31 19:07 ` Eric W. Biederman
2007-05-31 19:27 ` H. Peter Anvin
2007-05-31 20:22 ` Jeremy Fitzhardinge
2007-05-31 20:17 ` Jeremy Fitzhardinge
2007-05-31 20:07 ` Jeremy Fitzhardinge
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=465E7CA2.6090201@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=vgoyal@in.ibm.com \
--cc=virtualization@lists.osdl.org \
/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).