[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5266620602000078000FCA48@nat28.tlf.novell.com>
Date: Tue, 22 Oct 2013 10:31:18 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "Ian Campbell" <ian.campbell@...rix.com>
Cc: <ross.philipson@...rix.com>, <stefano.stabellini@...citrix.com>,
<grub-devel@....org>, <david.woodhouse@...el.com>,
<richard.l.maliszewski@...el.com>, <xen-devel@...ts.xen.org>,
<boris.ostrovsky@...cle.com>,
"Daniel Kiper" <daniel.kiper@...cle.com>, <konrad.wilk@...cle.com>,
"Peter Jones" <pjones@...hat.com>, <linux-kernel@...r.kernel.org>,
<keir@....org>
Subject: Re: EFI and multiboot2 devlopment work for Xen
>>> On 22.10.13 at 11:26, Ian Campbell <ian.campbell@...rix.com> wrote:
> AIUI "efilinux" is somewhat badly named and does not use the Linux Boot
> Protocol (i.e. the (b)zImage stuff with real mode entry point) either.
> It actually loads and executes the kernel binary as a PE/COFF executable
> (the native UEFI binary executable format). xen.efi is a PE/COFF binary
> too and could equally well be launched by linuxefi in this way.
Except that unless I'm mistaken "linuxefi" still expects to find certain
Linux-specific internal data structures inside the PE image, which I
don't see us wanting to be emulating. That's the main difference to
"chainloader" afaict.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists