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
Subject: [PATCH 0/1] x86/PVHv2: Add memory map pointer to hvm_start_info struct
Date: Fri,  2 Mar 2018 12:54:28 -0800	[thread overview]
Message-ID: <1520024069-30692-1-git-send-email-maran.wilson@oracle.com> (raw)

Here is the patch 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

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

 xen/include/public/arch-x86/hvm/start_info.h | 51 +++++++++++++++++-
 1 file changed, 50 insertions(+), 1 deletion(-)

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

             reply	other threads:[~2018-03-02 20:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 20:54 Maran Wilson [this message]
2018-03-02 20:54 ` [PATCH 1/1] x86/PVHv2: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-03-02 21:20   ` Konrad Rzeszutek Wilk
2018-03-02 22:29     ` Maran Wilson
2018-03-06 19:08       ` Daniel Kiper
2018-03-05  9:16   ` Jan Beulich
2018-03-13 10:50   ` Roger Pau Monné
2018-03-13 16:20     ` Maran Wilson
2018-03-13 16:34       ` Jan Beulich
2018-03-13 16:55         ` Maran Wilson
2018-03-13 17:16           ` Roger Pau Monné
2018-03-13 18:09             ` Maran Wilson
2018-03-14  7:43           ` Jan Beulich
2018-03-13 16:38       ` Roger Pau Monné

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=1520024069-30692-1-git-send-email-maran.wilson@oracle.com \
    --to=maran.wilson@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.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).