From: Paolo Bonzini <pbonzini@redhat.com>
To: Maran Wilson <maran.wilson@oracle.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 18:16:14 +0100 [thread overview]
Message-ID: <b964c95d-8698-7dbb-648b-6d494eecd30b@redhat.com> (raw)
In-Reply-To: <c0b3db51-f0d6-b0fe-24bc-14c081d722d3@oracle.com>
On 29/11/2017 18:14, Maran Wilson wrote:
> 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.
Yes, please do an option ROM. I'll take care of porting it to qboot.
Thanks,
Paolo
prev parent reply other threads:[~2017-11-29 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 19:34 Maran Wilson
2017-11-28 19:41 ` Andrew Cooper
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 14:03 ` Boris Ostrovsky
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:47 ` Juergen Gross
2017-11-29 14:50 ` Paolo Bonzini
2017-11-29 14:52 ` Andrew Cooper
2017-11-30 18:23 ` Maran Wilson
2017-12-01 8:08 ` Paolo Bonzini
2017-12-07 23:03 ` Maran Wilson
2017-11-29 17:24 ` Maran Wilson
2017-11-29 8:59 ` Paolo Bonzini
2017-11-29 17:14 ` Maran Wilson
2017-11-29 17:16 ` 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=b964c95d-8698-7dbb-648b-6d494eecd30b@redhat.com \
--to=pbonzini@redhat.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=maran.wilson@oracle.com \
--cc=mingo@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 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®