mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Cc: boris.ostrovsky@oracle.com, 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, linus.walleij@linaro.org,
	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, Stefan Hajnoczi <stefanha@redhat.com>,
	Stefano Garzarella <sgarzare@redhat.com>,
	Liam Merwick <liam.merwick@oracle.com>,
	George Kennedy <george.kennedy@oracle.com>
Subject: Re: [PATCH v7 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Mon, 19 Nov 2018 19:25:43 +0100	[thread overview]
Message-ID: <a0156b30-2e67-b68b-d555-a255acf2098e@redhat.com> (raw)
In-Reply-To: <bf0112de-8ceb-d1e4-d787-bf6bde7a1f14@oracle.com>

On 16/11/18 18:17, Maran Wilson wrote:
> On 11/16/2018 2:46 AM, Paolo Bonzini wrote:
>> On 17/04/18 01:09, 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.
>> Hi Maran, what happened to this series (and to the QEMU work)?
> 
> Hi Paolo,
> 
> Thank you for the reminder. Sorry, I have been wanting to continue this
> work for a while now, but our team has been pulled in other directions
> and this one ended up getting temporarily pushed down the priority stack.
> 
> Let me discuss with my management and get back to you. I do want (and
> intend) to support and push this over the finish line.
> 
> In the meantime, if there are any folks out there with a specific
> business need for getting this done sooner rather than later

Well, we are interested in using this to avoid the decompression cost of
booting a "container-like" VM image.  I'm not sure what we will do about
that, but certainly getting this included in the upstream projects would
be a prerequisite.

If you really prefer to discuss things offlist, feel free to include me,
Stefan and Stefano.

Paolo

> and are
> able to invest a bit of time to collaborate on the remaining Qemu work,
> please feel free to ping me offline. We have some preliminary Qemu
> patches, but there is some additional work needed before they are ready
> wider review.
> 
> Thanks,
> -Maran

      reply	other threads:[~2018-11-19 18:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 23:09 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
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 [this message]

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=a0156b30-2e67-b68b-d555-a255acf2098e@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=george.kennedy@oracle.com \
    --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=liam.merwick@oracle.com \
    --cc=linus.walleij@linaro.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=sgarzare@redhat.com \
    --cc=stefanha@redhat.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

all inboxes | Powered by JetHome®