xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Maran Wilson <maran.wilson@oracle.com>
To: jbeulich@suse.com, andrew.cooper3@citrix.com,
	xen-devel@lists.xen.org, maran.wilson@oracle.com,
	boris.ostrovsky@oracle.com, roger.pau@citrix.com,
	ian.jackson@eu.citrix.com, wei.liu2@citrix.com
Subject: [PATCH v2 0/4] x86/PVHv2: Add memory map pointer to hvm_start_info struct
Date: Tue, 13 Mar 2018 16:31:36 -0700	[thread overview]
Message-ID: <1520983900-13977-1-git-send-email-maran.wilson@oracle.com> (raw)

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

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.

 tools/libxc/include/xc_dom.h                 |  8 ++-
 tools/libxc/xc_dom_x86.c                     | 21 +++++-
 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 | 63 +++++++++++++++++-
 7 files changed, 109 insertions(+), 7 deletions(-)

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


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

             reply	other threads:[~2018-03-13 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 23:31 Maran Wilson [this message]
2018-03-13 23:31 ` [PATCH v2 1/4] x86/PVHv2: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-03-14  7:55   ` Jan Beulich
2018-03-14 17:28     ` Boris Ostrovsky
2018-03-14 20:07       ` Maran Wilson
2018-03-15  7:22         ` Jan Beulich
2018-03-15  9:31           ` Roger Pau Monné
2018-03-15  7:12       ` Jan Beulich
2018-03-13 23:31 ` [PATCH v2 2/4] libxl: Move libxl__arch_domain_construct_memmap() earlier Maran Wilson
2018-03-13 23:31 ` [PATCH v2 3/4] libxl: Store PVH guest's e820 map in xc_dom_image Maran Wilson
2018-03-13 23:31 ` [PATCH v2 4/4] libxc: Pass e820 map to PVH guest via hvm_start_info Maran Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1520983900-13977-1-git-send-email-maran.wilson@oracle.com \
    --to=maran.wilson@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).