Re: [RFC PATCH v4 5/7] xen/pvh: Move Xen code for getting mem map via hcall out of common file

2018-02-28 Thread Juergen Gross
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.

Re: [RFC PATCH v4 5/7] xen/pvh: Move Xen code for getting mem map via hcall out of common file

2018-02-28 Thread Juergen Gross
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.

[RFC PATCH v4 5/7] xen/pvh: Move Xen code for getting mem map via hcall out of common file

2018-02-28 Thread Maran Wilson
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

[RFC PATCH v4 5/7] xen/pvh: Move Xen code for getting mem map via hcall out of common file

2018-02-28 Thread Maran Wilson
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