[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <af2b37f0-b048-bf8e-525c-b9fa4fac7fc0@suse.com>
Date: Thu, 1 Mar 2018 08:20:32 +0100
From: Juergen Gross <jgross@...e.com>
To: Maran Wilson <maran.wilson@...cle.com>, pbonzini@...hat.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
Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
rkrcmar@...hat.com, jpoimboe@...hat.com, bp@...e.de,
kirill.shutemov@...ux.intel.com, thomas.lendacky@....com,
luto@...nel.org, dave.hansen@...ux.intel.com, davem@...emloft.net,
gregkh@...uxfoundation.org, mchehab@...nel.org,
linus.walleij@...aro.org, rdunlap@...radead.org
Subject: Re: [RFC PATCH v4 4/7] xen/pvh: Move Xen specific PVH VM
initialization out of common code
On 28/02/18 19:28, 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: Juergen Gross <jgross@...e.com>
Juergen
Powered by blists - more mailing lists