Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751884Ab3JVJ7i (ORCPT ); Tue, 22 Oct 2013 05:59:38 -0400 Received: from nat28.tlf.novell.com ([130.57.49.28]:52287 "EHLO nat28.tlf.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751372Ab3JVJ7h convert rfc822-to-8bit (ORCPT ); Tue, 22 Oct 2013 05:59:37 -0400 Message-Id: <526668A502000078000FCA7B@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.2 Date: Tue, 22 Oct 2013 10:59:33 +0100 From: "Jan Beulich" To: "Ian Campbell" Cc: , , , , , , , "Daniel Kiper" , , "Peter Jones" , , Subject: Re: EFI and multiboot2 devlopment work for Xen References: <20131021125756.GA3626@debian70-amd64.local.net-space.pl> <20131021135437.GD1283@fenchurch.internal.datastacks.com> <20131021185758.GD3626@debian70-amd64.local.net-space.pl> <1382433990.1657.66.camel@hastur.hellion.org.uk> <5266620602000078000FCA48@nat28.tlf.novell.com> <1382435127.1657.70.camel@hastur.hellion.org.uk> In-Reply-To: <1382435127.1657.70.camel@hastur.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1428 Lines: 31 >>> On 22.10.13 at 11:45, Ian Campbell wrote: > On Tue, 2013-10-22 at 10:31 +0100, Jan Beulich wrote: >> >>> On 22.10.13 at 11:26, Ian Campbell 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. > > Ah, I'd been led to believe it was just the lack of a call to > ExitBootServices, but I didn't check. What you say sounds completely > plausible. > > Do you know what sort of Linux specific data structures are we talking > about? The setup header I would assume (i.e. the bits surrounding the "HdrS" signature). But I'm only guessing anyway. Jan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/