search for: bootparams_pfn

...hat %esi point to the boot_params block on entry. Unfortunately this conflicts with the normal Xen boot protocol, which starts with %esi pointing to a struct start_info. In order to implement this, I've had to muck up Gerd's nice clean layering a little bit. struct xc_dom_image now has a bootparams_pfn, which is set by the bzImage loader. Then, when xc_dom_x86 sees that its non-NULL when setting up the initial vcpu state, it points %esi that rather than start_info (and the boot_params contains a pointer to start_info). Fortunately, the embedded ELF file makes it easy to reuse a lot of the exist...

...hat %esi point to the boot_params block on entry. Unfortunately this conflicts with the normal Xen boot protocol, which starts with %esi pointing to a struct start_info. In order to implement this, I've had to muck up Gerd's nice clean layering a little bit. struct xc_dom_image now has a bootparams_pfn, which is set by the bzImage loader. Then, when xc_dom_x86 sees that its non-NULL when setting up the initial vcpu state, it points %esi that rather than start_info (and the boot_params contains a pointer to start_info). Fortunately, the embedded ELF file makes it easy to reuse a lot of the exist...

...hat %esi point to the boot_params block on entry. Unfortunately this conflicts with the normal Xen boot protocol, which starts with %esi pointing to a struct start_info. In order to implement this, I've had to muck up Gerd's nice clean layering a little bit. struct xc_dom_image now has a bootparams_pfn, which is set by the bzImage loader. Then, when xc_dom_x86 sees that its non-NULL when setting up the initial vcpu state, it points %esi that rather than start_info (and the boot_params contains a pointer to start_info). Fortunately, the embedded ELF file makes it easy to reuse a lot of the exist...