Use the Kconfig generated CONFIG_COMPAT defines in the code base.

CC: Keir Fraser <k...@xen.org>
CC: Jan Beulich <jbeul...@suse.com>
CC: Andrew Cooper <andrew.coop...@citrix.com>
Signed-off-by: Doug Goldstein <car...@cardoe.com>
---
 config/x86_64.mk     | 1 -
 xen/arch/x86/Kconfig | 7 +++++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/config/x86_64.mk b/config/x86_64.mk
index f12d549..85fa27c 100644
--- a/config/x86_64.mk
+++ b/config/x86_64.mk
@@ -2,7 +2,6 @@ CONFIG_X86 := y
 CONFIG_X86_64 := y
 CONFIG_X86_$(XEN_OS) := y
 
-CONFIG_COMPAT := y
 CONFIG_MIGRATE := y
 CONFIG_XCUTILS := y
 
diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig
index 07e366d..9c5abc0 100644
--- a/xen/arch/x86/Kconfig
+++ b/xen/arch/x86/Kconfig
@@ -24,6 +24,13 @@ config ARCH_DEFCONFIG
 
 menu "Architecture Features"
 
+config COMPAT
+       def_bool y
+       help
+         32-bit interface support on 64-bit Xen which is used for both
+         HVM and PV guests. HVMLoader makes 32-bit hypercalls irrespective
+         of the destination runmode of the guest.
+
 endmenu
 
 source "common/Kconfig"
-- 
2.4.10


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to