[Xen-devel] [PATCH v3 0/4] x86/PVHv2: Add memory map pointer to hvm_start_info struct

[Maran Wilson <maran.wilson@xxxxxxxxxx>]

Here is the patch series for updating the canonical definition of the
hvm_start_info struct corresponding to the discussion happening on the
linux-kernel and kvm mailing lists regarding Qemu/KVM use of the PVH
entry point:

   KVM: x86: Allow Qemu/KVM to use PVH entry point
   https://lkml.org/lkml/2018/2/28/1121

Patch 1 contains all the changes to the hvm_start_info struct and
patches 2-4 modify Xen to use the new memory map fields of the structure.

Changes since v2:
 * Better definition of the memory map types including addition of new
   symbols and tightening up the comments as suggested.
 * Added a couple of BUILD_BUG_ON() statements to the c code in patch #4
   to document and verify the relationship between these memory types
   and e820 types.

Changes since v1:
 * Made updates to code comments as suggested by Jan and Roger, including
   better definition of the memory map type field.   
 * Boris provided additional patches to populate the new fields in the
   hvm_start_info struct as Jan (and later Roger also) had requested.


Boris Ostrovsky (3):
  libxl: Move libxl__arch_domain_construct_memmap() earlier
  libxl: Store PVH guest's e820 map in xc_dom_image
  libxc: Pass e820 map to PVH guest via hvm_start_info

Maran Wilson (1):
  x86/PVHv2: Add memory map pointer to hvm_start_info struct

 tools/libxc/include/xc_dom.h                 |  8 +++-
 tools/libxc/xc_dom_x86.c                     | 30 ++++++++++++-
 tools/libxl/libxl_create.c                   |  2 +-
 tools/libxl/libxl_dom.c                      | 12 +++--
 tools/libxl/libxl_internal.h                 |  1 +
 tools/libxl/libxl_x86.c                      |  9 ++++
 xen/include/public/arch-x86/hvm/start_info.h | 66 +++++++++++++++++++++++++++-
 7 files changed, 121 insertions(+), 7 deletions(-)

-- 
1.8.3.1


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel