On 28/02/18 19:28, Maran Wilson wrote: > We need to refactor PVH entry code so that support for other hypervisors > like Qemu/KVM can be added more easily. > > The original design for PVH entry in Xen guests relies on being able to > obtain the memory map from the hypervisor using a hypercall. When we > extend the PVH entry ABI to support other hypervisors like Qemu/KVM, > a new mechanism will be added that allows the guest to get the memory > map without needing to use hypercalls. > > For Xen guests, the hypercall approach will still be supported. In > preparation for adding support for other hypervisors, we can move the > code that uses hypercalls into the Xen specific file. This will allow us > to compile kernels in the future without CONFIG_XEN that are still capable > of being booted as a Qemu/KVM guest via the PVH entry point. > > Signed-off-by: Maran Wilson <maran.wil...@oracle.com>
Reviewed-by: Juergen Gross <jgr...@suse.com> Juergen
