From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Maran Wilson <maran.wilson@oracle.com>,
Paolo Bonzini <pbonzini@redhat.com>,
x86@kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
jgross@suse.com
Cc: bp@suse.de, dave.hansen@linux.intel.com, davem@davemloft.net,
gregkh@linuxfoundation.org, hpa@zytor.com, jpoimboe@redhat.com,
kirill.shutemov@linux.intel.com, luto@kernel.org,
mchehab@kernel.org, mingo@redhat.com, rdunlap@infradead.org,
tglx@linutronix.de, thomas.lendacky@amd.com, hch@infradead.org,
roger.pau@citrix.com, rkrcmar@redhat.com
Subject: Re: [PATCH v8 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Wed, 12 Dec 2018 13:17:01 -0500 [thread overview]
Message-ID: <f6fa8b66-393d-f36d-aef9-137f1a254400@oracle.com> (raw)
In-Reply-To: <faae2cec-1ff2-74eb-69c8-b75f64cfca3a@oracle.com>
On 12/12/18 1:09 PM, Maran Wilson wrote:
> On 12/6/2018 1:21 PM, Paolo Bonzini wrote:
>> On 06/12/18 07:02, Maran Wilson wrote:
>>> For certain applications it is desirable to rapidly boot a KVM virtual
>>> machine. In cases where legacy hardware and software support within the
>>> guest is not needed, Qemu should be able to boot directly into the
>>> uncompressed Linux kernel binary without the need to run firmware.
>>>
>>> There already exists an ABI to allow this for Xen PVH guests and the
>>> ABI
>>> is supported by Linux and FreeBSD:
>>>
>>> https://xenbits.xen.org/docs/unstable/misc/pvh.html
>>>
>>> This patch series would enable Qemu to use that same entry point for
>>> booting KVM guests.
>> Thanks! I should be able to post a Tested-by next Monday. Boris, are
>> you going to pick it up for 4.21?
Just realized I never answered this --- yes, I am. Now that BorisP.
acked this, having your T-b would be good.
-boris
>
> Hi Paolo,
>
> Are you still planning on running some testing of your own for these
> patches? Should Boris wait to hear from you before moving forward?
>
> Thanks,
> -Maran
>
>> Paolo
>
next prev parent reply other threads:[~2018-12-12 18:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 6:02 [PATCH v8 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-06 6:04 ` [PATCH v8 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH Maran Wilson
2018-12-06 22:11 ` Paolo Bonzini
2018-12-06 22:34 ` Boris Ostrovsky
2018-12-06 22:49 ` Paolo Bonzini
2018-12-06 23:11 ` Boris Ostrovsky
2018-12-06 23:30 ` Paolo Bonzini
2018-12-06 23:36 ` [Xen-devel] " Andrew Cooper
2018-12-07 6:02 ` Juergen Gross
2018-12-07 13:41 ` Paolo Bonzini
2018-12-07 13:50 ` Juergen Gross
2018-12-07 13:52 ` Paolo Bonzini
2018-12-07 13:58 ` Juergen Gross
2018-12-07 15:14 ` Paolo Bonzini
2018-12-07 18:21 ` Maran Wilson
2018-12-06 6:04 ` [PATCH v8 2/7] xen/pvh: Move PVH entry code out of Xen specific tree Maran Wilson
2018-12-06 6:05 ` [PATCH v8 3/7] xen/pvh: Create a new file for Xen specific PVH code Maran Wilson
2018-12-06 6:05 ` [PATCH v8 4/7] xen/pvh: Move Xen specific PVH VM initialization out of common file Maran Wilson
2018-12-06 6:05 ` [PATCH v8 5/7] xen/pvh: Move Xen code for getting mem map via hcall " Maran Wilson
2018-12-06 6:06 ` [PATCH v8 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-12-06 6:06 ` [PATCH v8 7/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-06 22:05 ` Paolo Bonzini
2018-12-06 21:21 ` [PATCH v8 0/7] " Paolo Bonzini
2018-12-06 21:37 ` Borislav Petkov
2018-12-06 21:58 ` Boris Ostrovsky
2018-12-06 22:14 ` Paolo Bonzini
2018-12-07 10:25 ` Borislav Petkov
2018-12-07 16:07 ` [Xen-devel] " Boris Ostrovsky
2018-12-07 19:22 ` Borislav Petkov
2018-12-12 18:09 ` Maran Wilson
2018-12-12 18:17 ` Boris Ostrovsky [this message]
2018-12-13 13:13 ` 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=f6fa8b66-393d-f36d-aef9-137f1a254400@oracle.com \
--to=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=pbonzini@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).