From: Borislav Petkov <bp@alien8.de>
To: Maran Wilson <maran.wilson@oracle.com>
Cc: x86@kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com, jgross@suse.com, 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, 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
Subject: Re: [PATCH v9 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Wed, 12 Dec 2018 21:39:02 +0100 [thread overview]
Message-ID: <20181212203901.GI6653@zn.tnic> (raw)
In-Reply-To: <5fc083d4-1dbd-f2f9-3059-0e3e8dda9b25@oracle.com>
On Tue, Dec 11, 2018 at 11:29:21AM -0800, Maran Wilson wrote:
> Is your question about what options you need to provide to Qemu? Or is your
> question about the SW implementation choices?
>
> Assuming the former...
Yeah, that's what I wanted to know. But looking at it, I'm booting
bzImage here just as quickly and as flexible so I don't see the
advantage of this new method for my use case here of booting kernels
in qemu.
But maybe there's a good use case where firmware is slow and one doesn't
really wanna noodle through it or when one does start a gazillion VMs
per second or whatever...
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-12-12 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 19:05 [PATCH v9 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-10 19:07 ` [PATCH v9 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH Maran Wilson
2018-12-11 13:22 ` Borislav Petkov
2018-12-10 19:07 ` [PATCH v9 2/7] xen/pvh: Move PVH entry code out of Xen specific tree Maran Wilson
2018-12-10 19:08 ` [PATCH v9 3/7] xen/pvh: Create a new file for Xen specific PVH code Maran Wilson
2018-12-10 19:08 ` [PATCH v9 4/7] xen/pvh: Move Xen specific PVH VM initialization out of common file Maran Wilson
2018-12-10 19:08 ` [PATCH v9 5/7] xen/pvh: Move Xen code for getting mem map via hcall " Maran Wilson
2018-12-10 19:09 ` [PATCH v9 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-12-10 19:09 ` [PATCH v9 7/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-11 13:18 ` [PATCH v9 0/7] " Borislav Petkov
2018-12-11 19:29 ` Maran Wilson
2018-12-12 20:39 ` Borislav Petkov [this message]
2018-12-12 21:56 ` Maran Wilson
2018-12-13 13:15 ` Paolo Bonzini
2018-12-14 23:13 ` Boris Ostrovsky
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=20181212203901.GI6653@zn.tnic \
--to=bp@alien8.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--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=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maran.wilson@oracle.com \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=roger.pau@citrix.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;
as well as URLs for NNTP newsgroup(s).