[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] EFI and multiboot2 devlopment work for Xen
- To: The development of GNU GRUB <grub-devel@xxxxxxx>
- From: Vladimir 'Ï-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
- Date: Wed, 23 Oct 2013 19:01:55 +0200
- Cc: mjg59@xxxxxxxxxxxxx, keir@xxxxxxx, david.woodhouse@xxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, daniel.kiper@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxx, Jan Beulich <jbeulich@xxxxxxxx>, ross.philipson@xxxxxxxxxx, richard.l.maliszewski@xxxxxxxxx, boris.ostrovsky@xxxxxxxxxx, ian.campbell@xxxxxxxxxx
- Delivery-date: Wed, 23 Oct 2013 17:04:04 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
> GrUB - which iiuc stays in memory
> after transferring control - could export its file system support to its
> descendants).
Xen shouldn't need to load any file after multiboot2 entry point. The
needed files would already be in memory with pointers to them passed.
If you insist on being able to load directly from EFI, then IMO the best
way is to have a PE executable with one of sections containing Xen and
code which would load remaining files to memory and call common entry point.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
