From: Maran Wilson <maran.wilson@oracle.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Juergen Gross" <jgross@suse.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, 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: Thu, 30 Nov 2017 10:23:17 -0800 [thread overview]
Message-ID: <ac4c7e15-2715-b889-9ae5-42b3c5baa332@oracle.com> (raw)
In-Reply-To: <25d6db63-a57d-b15c-2d43-e96c506b4824@redhat.com>
On 11/29/2017 6:44 AM, Paolo Bonzini wrote:
> I actually like this patch, except that I'd get the e820 memory map from
> fw_cfg (see the first part of
> https://github.com/bonzini/qboot/blob/master/fw_cfg.c, and extract_e820
> inhttps://github.com/bonzini/qboot/blob/master/main.c) instead of the
> second module.
Hi Paolo,
I want to make sure I understand exactly what you are suggesting...
Are you saying the Linux PVH entry code (such as init_pvh_bootparams())
should use the fw_cfg interface to read the e820 memory map data and put
it into the zeropage? Basically, keeping the patch very much like it
already is, just extracting the e820 data via the fw_cfg interface
instead of from the second module of start_info struct?
If that is the case, I guess I'm a bit hesitant to throw the QEMU
specific fw_cfg interface into the mix on the Linux PVH side when the
existing PVH ABI already seems to contain an interface for passing
modules/blobs to the guest. But if you feel there is a compelling reason
to use the fw_cfg interface here, I'm happy to explore that approach
further.
Thanks,
-Maran
next prev parent reply other threads:[~2017-11-30 18:23 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 [this message]
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
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=ac4c7e15-2715-b889-9ae5-42b3c5baa332@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.