[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 12 Dec 2018 21:39:02 +0100
From: Borislav Petkov <bp@...en8.de>
To: Maran Wilson <maran.wilson@...cle.com>
Cc: x86@...nel.org, xen-devel@...ts.xenproject.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
pbonzini@...hat.com, jgross@...e.com, boris.ostrovsky@...cle.com,
bp@...e.de, dave.hansen@...ux.intel.com, davem@...emloft.net,
gregkh@...uxfoundation.org, hpa@...or.com, jpoimboe@...hat.com,
kirill.shutemov@...ux.intel.com, luto@...nel.org,
mchehab@...nel.org, mingo@...hat.com, rdunlap@...radead.org,
tglx@...utronix.de, thomas.lendacky@....com, hch@...radead.org,
roger.pau@...rix.com, rkrcmar@...hat.com
Subject: Re: [PATCH v9 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
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.
Powered by blists - more mailing lists