[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180228211053.GM11576@char.us.oracle.com>
Date: Wed, 28 Feb 2018 16:10:53 -0500
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Maran Wilson <maran.wilson@...cle.com>
Cc: pbonzini@...hat.com, jgross@...e.com, boris.ostrovsky@...cle.com,
roger.pau@...rix.com, andrew.cooper3@...rix.com, hch@...radead.org,
JBeulich@...e.com, x86@...nel.org, xen-devel@...ts.xenproject.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
thomas.lendacky@....com, dave.hansen@...ux.intel.com,
rkrcmar@...hat.com, gregkh@...uxfoundation.org, mchehab@...nel.org,
hpa@...or.com, linus.walleij@...aro.org, mingo@...hat.com,
rdunlap@...radead.org, luto@...nel.org, jpoimboe@...hat.com,
tglx@...utronix.de, bp@...e.de, davem@...emloft.net,
kirill.shutemov@...ux.intel.com
Subject: Re: [Xen-devel] [RFC PATCH v4 4/7] xen/pvh: Move Xen specific PVH VM
initialization out of common code
On Wed, Feb 28, 2018 at 10:28:00AM -0800, Maran Wilson wrote:
> We need to refactor PVH entry code so that support for other hypervisors
> like Qemu/KVM can be added more easily.
>
> This patch moves the small block of code used for initializing Xen PVH
> virtual machines into the Xen specific file. This initialization is not
> going to be needed for Qemu/KVM guests. Moving it out of the common file
> is going to allow us to compile kernels in the future without CONFIG_XEN
> that are still capable of being booted as a Qemu/KVM guest via the PVH
> entry point.
>
> Signed-off-by: Maran Wilson <maran.wilson@...cle.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Thank you!
Powered by blists - more mailing lists