From: Rusty Russell <rusty@rustcorp.com.au>
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>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [patch rfc wip] first cut of ELF bzImage
Date: Thu, 31 May 2007 18:12:38 +1000 [thread overview]
Message-ID: <1180599158.11133.34.camel@localhost.localdomain> (raw)
In-Reply-To: <465E7EC0.6080108@goop.org>
On Thu, 2007-05-31 at 00:52 -0700, Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
> > 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.
>
> I'm not sure why you say that. Rusty managed to get unmodified
> bzImage's booting in lguest within a few hours of hacking. I don't
> expect Xen would be much different.
Yes, it only required V=P mappings and skipping over the cli & segment
reloads.
It's becoming pretty clear that booting with V=P mappings is in fact the
right thing to do, so I don't think that's a real restriction. And
we've discussed the cli and segment reloads already.
I understand the desire to restart from scratch, but I don't think we're
there yet....
Rusty.
next prev parent reply other threads:[~2007-05-31 8:12 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
2007-05-31 7:52 ` Jeremy Fitzhardinge
2007-05-31 8:12 ` Rusty Russell [this message]
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=1180599158.11133.34.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.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).