From: Paolo Bonzini <pbonzini@redhat.com>
To: "Juergen Gross" <jgross@suse.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: Maran Wilson <maran.wilson@oracle.com>,
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: Wed, 29 Nov 2017 15:50:27 +0100 [thread overview]
Message-ID: <1a529a09-2b84-a730-7518-158489303377@redhat.com> (raw)
In-Reply-To: <e46a8232-22c0-e437-6bd8-e51844a60eaa@suse.com>
On 29/11/2017 15:47, Juergen Gross wrote:
> On 29/11/17 15:44, Paolo Bonzini wrote:
>> In either case, you would have a new option ROM. It could either be
>> very simple and similar to multiboot.S, or it could be larger and do the
>> same task as xen-pvh.S and enlighten_pvh.c (then get the address of
>> startup_32 or startup_64 from FW_CFG_KERNEL_ENTRY and jump there). The
>> ugly part is that the option ROM would have to know more details about
>> what it is going to boot, including for example whether it's 32-bit or
>> 64-bit, so I don't really think it is a good idea.
>
> As grub2 doesn't have to know, qemu shouldn't have to know either.
That would be exactly what linuxboot-dma.c does already, but it's slower
than PVH because Linux has to uncompress itself.
The above thought experiment would make QEMU able to boot a PVH kernel
without any changes to Linux.
Paolo
next prev parent reply other threads:[~2017-11-29 14:50 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 [this message]
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
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=1a529a09-2b84-a730-7518-158489303377@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®