[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH for-xen-4.5 v4 00/18] xen: Break multiboot (v1) dependency and add multiboot2 support
- To: "Daniel Kiper" <daniel.kiper@xxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Thu, 23 Oct 2014 17:04:53 +0100
- Cc: Juergen Gross <JGross@xxxxxxxx>, keir@xxxxxxx, ian.campbell@xxxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, roy.franz@xxxxxxxxxx, ning.sun@xxxxxxxxx, ross.philipson@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, qiaowei.ren@xxxxxxxxx, richard.l.maliszewski@xxxxxxxxx, gang.wei@xxxxxxxxx, fu.wei@xxxxxxxxxx
- Delivery-date: Thu, 23 Oct 2014 16:04:58 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 23.10.14 at 17:50, <daniel.kiper@xxxxxxxxxx> wrote:
> OK, AIUI you suggest that I should parse all multiboot2 data in reloc.c
> and put all things in multiboot1 struct which lives on trampoline. Then
> I should add global variables for EFI_HANDLE and EFI_SYSTEM_TABLE somewhere
> in x86_64.S and initialize them from reloc.c. After that I should call
> efi_start() immediately after reloc() if Xen runs on EFI platform.
I wouldn't call this "parse", but beyond that it sounds roughly right.
Whether you need global variables or can find some other
mechanism to propagate the EFI specific things is secondary.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
