From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: booting Xen from EFI
Date: Wed, 15 Jun 2011 16:58:21 +0100 [thread overview]
Message-ID: <CA1E952D.1C426%keir.xen@gmail.com> (raw)
In-Reply-To: <4DF8EA3902000078000476BB@nat28.tlf.novell.com>
On 15/06/2011 16:22, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> On 15.06.11 at 16:55, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 15/06/2011 13:48, "Jan Beulich" <JBeulich@novell.com> wrote:
>>> 3) GrUB decompresses simple gzip-ed binaries (i.e. the traditional
>>> non-bzImage kernel), but with EFI Xen will need to do so itself.
>>> The most obvious choice would seem be to allow for all currently
>>> supported compression methods to not only be used inside a
>>> bzImage container, but also on a plain ELF binary.
>>
>> I don't really understand the problem. As long as we don't get yet another
>> pile of decompressors in the tree I don't really care either.
>
> Xen doesn't currently understand a compressed (gzip or other)
> ELF image, it can only deal with compressed payloads of bzImage
> containers.
>
> And no, it would just mean hooking up the existing decompressors
> via a second path.
Ah yes I see. That makes sense.
-- Keir
next prev parent reply other threads:[~2011-06-15 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 12:48 booting Xen from EFI Jan Beulich
2011-06-15 14:55 ` Keir Fraser
2011-06-15 15:22 ` Jan Beulich
2011-06-15 15:58 ` Keir Fraser [this message]
2011-06-17 16:15 ` Chris Dalton
2011-06-21 14:21 ` Konrad Rzeszutek Wilk
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=CA1E952D.1C426%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.