Isaku Yamahata wrote:
XEN_DOMCTL_arch_setup hypercall sets up EFI memory map,
xen-faked EFI firmware and etc. So it should be called before
loading kernel/initrd images.
Why is this order important?
How about adding new methods like setup_meminit, setup_firmware, setup_boot
(Or please suggest better names.) to struct xc_dom_loader?
Certainly not to "struct xc_dom_loader", that one is for binary formats
such as ELF and thus architecture-independant.
Maybe we could put that into "struct xc_dom_arch". I've intentionally
tried to keep the code which does hypercalls separately though.
And call setup_meminit at xc_dom_boot_mem_init(),
setup_firmware at the beginning of xc_dom_build_image(),
setup_boot at xc_dom_boot_image().
Only the xc_dom_boot_*() functions are supposed to invoke hypercalls.
Thus the firmware setup can happen either at the end of
xc_dom_boot_mem_init or at the start of xc_dom_boot_image.
cheers,
Gerd
8 messages in com.xensource.lists.xen-ia64-develRe: [Xen-devel] [PATCH] new domain bu...
.patch