From: Maran Wilson <maran.wilson@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
boris.ostrovsky@oracle.com, jgross@suse.com, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
roger.pau@citrix.com, rkrcmar@redhat.com, JBeulich@suse.com,
andrew.cooper3@citrix.com, kvm@vger.kernel.org
Subject: Re: [RFC PATCH] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Wed, 29 Nov 2017 09:14:11 -0800 [thread overview]
Message-ID: <c0b3db51-f0d6-b0fe-24bc-14c081d722d3__2651.62523505769$1511975740$gmane$org@oracle.com> (raw)
In-Reply-To: <d94b394d-7acb-0de7-62a7-77ad39fcc268@redhat.com>
On 11/29/2017 12:59 AM, Paolo Bonzini wrote:
> On 28/11/2017 20:34, 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/hvmlite.html
>>
>> This PoC patch enables Qemu to use that same entry point for booting KVM
>> guests.
> Nice! So QEMU would parse the ELF file just like for multiboot, find
> the ELF note, and then prepare an hvmlite boot info struct instead of
> the multiboot one?
Yes, exactly.
> There would then be a new option ROM, very similar
> to multiboot.S.
That is one option. I guess this gets into a discussion about the QEMU
side of the upcoming patches that would follow ...
I'm currently just initializing the CPU state in QEMU for testing since
there is such minimal (non Linux specific) setup that is required by the
ABI. And (borrowing from the Intel clear container patches) that VM
setup is only performed when user selects the "nofw" option with the q35
model. But yeah, if folks think it important to move all such machine
state initialization out of QEMU and into an option ROM, I can look into
coding it up that way for the QEMU patches.
Thanks,
-Maran
> Thanks,
>
> Paolo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2017-11-29 17:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 19:34 [RFC PATCH] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2017-11-28 19:34 ` Maran Wilson
2017-11-28 19:41 ` Andrew Cooper
2017-11-28 19:41 ` Andrew Cooper
2017-11-28 19:41 ` Andrew Cooper
2017-11-28 19:58 ` Christoph Hellwig
2017-11-28 19:58 ` Christoph Hellwig
2017-11-29 8:21 ` Juergen Gross
2017-11-29 8:50 ` Roger Pau Monné
2017-11-29 8:50 ` Roger Pau Monné
2017-11-29 14:03 ` Boris Ostrovsky
2017-11-29 14:11 ` Juergen Gross
2017-11-29 14:11 ` Juergen Gross
2017-11-29 14:18 ` Roger Pau Monné
2017-11-29 14:25 ` Boris Ostrovsky
2017-11-29 14:44 ` Paolo Bonzini
2017-11-29 14:44 ` Paolo Bonzini
2017-11-29 14:47 ` Juergen Gross
2017-11-29 14:47 ` Juergen Gross
2017-11-29 14:50 ` Paolo Bonzini
2017-11-29 14:50 ` Paolo Bonzini
2017-11-29 14:52 ` Andrew Cooper
2017-11-29 14:52 ` Andrew Cooper
2017-11-30 18:23 ` Maran Wilson
2017-11-30 18:23 ` Maran Wilson
2017-12-01 8:08 ` Paolo Bonzini
2017-12-01 8:08 ` Paolo Bonzini
2017-12-07 23:03 ` Maran Wilson
2017-12-07 23:03 ` Maran Wilson
2017-11-29 14:25 ` Boris Ostrovsky
2017-11-29 14:18 ` Roger Pau Monné
2017-11-29 14:03 ` Boris Ostrovsky
2017-11-29 17:24 ` Maran Wilson
2017-11-29 17:24 ` Maran Wilson
2017-11-29 8:21 ` Juergen Gross
2017-11-29 8:59 ` Paolo Bonzini
2017-11-29 17:14 ` Maran Wilson [this message]
2017-11-29 17:14 ` Maran Wilson
2017-11-29 17:16 ` Paolo Bonzini
2017-11-29 17:16 ` Paolo Bonzini
2017-11-29 8:59 ` 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='c0b3db51-f0d6-b0fe-24bc-14c081d722d3__2651.62523505769$1511975740$gmane$org@oracle.com' \
--to=maran.wilson@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=roger.pau@citrix.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.