From: Paolo Bonzini <pbonzini@redhat.com>
To: Maran Wilson <maran.wilson@oracle.com>,
x86@kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
jgross@suse.com, hpa@zytor.com, mingo@redhat.com,
tglx@linutronix.de
Cc: boris.ostrovsky@oracle.com, bp@suse.de,
dave.hansen@linux.intel.com, davem@davemloft.net,
gregkh@linuxfoundation.org, jpoimboe@redhat.com,
kirill.shutemov@linux.intel.com, luto@kernel.org,
mchehab@kernel.org, rdunlap@infradead.org,
thomas.lendacky@amd.com, hch@infradead.org, roger.pau@citrix.com,
rkrcmar@redhat.com
Subject: Re: [PATCH v7 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Fri, 18 May 2018 13:31:49 +0200 [thread overview]
Message-ID: <911f4739-1a92-8ad3-4c0c-5541312c39fb@redhat.com> (raw)
In-Reply-To: <505290b7-416f-cc97-35ff-e416ceb532c2@oracle.com>
On 16/05/2018 22:27, Maran Wilson wrote:
> Friendly ping. I am hopeful one of the x86 and/or KVM maintainers has a
> few cycles to spare to look this over.
>
> And thanks to everyone who has helped thus far by providing valuable
> feedback and reviewing.
>
> https://lkml.org/lkml/2018/4/16/1002
KVM bits look fine. This would be the right time to post the QEMU
patches...
Paolo
next prev parent reply other threads:[~2018-05-18 11:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 23:09 [PATCH v7 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-04-16 23:11 ` [PATCH v7 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH Maran Wilson
2018-04-17 6:18 ` Juergen Gross
2018-04-16 23:11 ` [PATCH v7 2/7] xen/pvh: Move PVH entry code out of Xen specific tree Maran Wilson
2018-04-17 6:24 ` Juergen Gross
2018-04-16 23:12 ` [PATCH v7 3/7] xen/pvh: Create a new file for Xen specific PVH code Maran Wilson
2018-04-17 6:29 ` Juergen Gross
2018-04-16 23:12 ` [PATCH v7 4/7] xen/pvh: Move Xen specific PVH VM initialization out of common file Maran Wilson
2018-04-16 23:12 ` [PATCH v7 5/7] xen/pvh: Move Xen code for getting mem map via hcall " Maran Wilson
2018-04-16 23:13 ` [PATCH v7 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-04-17 6:30 ` Juergen Gross
2018-04-16 23:13 ` [PATCH v7 7/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-04-17 6:41 ` Juergen Gross
2018-04-18 8:11 ` [PATCH v7 0/7] " Linus Walleij
2018-05-02 21:37 ` Maran Wilson
2018-05-16 20:27 ` Maran Wilson
2018-05-18 11:31 ` Paolo Bonzini [this message]
2018-05-23 16:56 ` Maran Wilson
2018-11-16 10:46 ` Paolo Bonzini
2018-11-16 17:17 ` Maran Wilson
2018-11-19 18:25 ` Paolo Bonzini
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=911f4739-1a92-8ad3-4c0c-5541312c39fb@redhat.com \
--to=pbonzini@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maran.wilson@oracle.com \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=roger.pau@citrix.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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).