Hi,
On 03/20/2018 12:18 PM, Maran Wilson wrote:
In order to pave the way for hypervisors other then Xen to use the PVHthan
entry point for VMs, we need to factor the PVH entry code into Xen specificYou don't need two (2) "bool"s here. And 'n' is already the default, so just
and hypervisor agnostic components. The first step in doing that, is to
create a new config option for PVH entry that can be enabled
independently from CONFIG_XEN.
Signed-off-by: Maran Wilson <maran.wilson@xxxxxxxxxx>
---
arch/x86/Kconfig | 7 +++++++
arch/x86/kernel/head_64.S | 4 ++--
arch/x86/xen/Kconfig | 3 ++-
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index eb7f43f23521..58831320b5d2 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -791,6 +791,13 @@ config KVM_GUEST
underlying device model, the host provides the guest with
timing infrastructure such as time of day, and system time
+config PVH
+ bool "Support for running PVH guests"
+ def_bool n
drop the second line.
+ ---help---
+ This option enables the PVH entry point for guest virtual machines
+ as specified in the x86/HVM direct boot ABI.
+
config KVM_DEBUG_FS
bool "Enable debug information for KVM Guests in debugfs"
depends on KVM_GUEST && DEBUG_FS