[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5266A37802000078000FCB2D@nat28.tlf.novell.com>
Date: Tue, 22 Oct 2013 15:10:32 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "Ian Campbell" <ian.campbell@...rix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.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>,
"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 15:53, Ian Campbell <ian.campbell@...rix.com> wrote:
> On Tue, 2013-10-22 at 09:42 -0400, Konrad Rzeszutek Wilk wrote:
>
>> Looking at the Fedora GRUB2 source, the 'struct linux_kernel_header' is
> defined
>> in the linux/Documentation/x86/boot.txt and hpa is pretty strict
>> about making it backwards compatible. It also seems to support Xen!
>>
>> (Interestingly enough we do have this structure in the code: see
>> setup_header in arch/x86/bzimage.c)
>
> There will be another usage in tools/libxc/...bzimage too
>
> FWIW I think we only use this stuff for the magic number/version and the
> payload_offset/length fields, which we do in order to extract the
> payload (ELF file) for booting dom0 and domU. It's not AFAIK used for
> booting Xen itself or lets say, that's not why I added it ;-)).
Indeed, we only use this to handle bzImage type kernels.
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