This only added dead code. Use "if" instead of "depends on" to make
(halfway) clear that other guest options should also go in the same
block. Move the option down such that the shim related options get
presented first, avoiding to ask the question when the answer may end
up being discarded.
While in the neighborhood also bring PV_SHIM_EXCLUSIVE into more
"canonical" shape.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Wei Liu <wl@xen.org>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
config GUEST
bool
-config HYPERV_GUEST
- bool "Hyper-V Guest"
- select GUEST
- ---help---
- Support for Xen detecting when it is running under Hyper-V.
-
- If unsure, say N.
-
config XEN_GUEST
bool "Xen Guest"
select GUEST
If unsure, say Y.
config PV_SHIM_EXCLUSIVE
- def_bool n
- prompt "PV Shim Exclusive"
+ bool "PV Shim Exclusive"
depends on PV_SHIM
---help---
Build Xen in a way which unconditionally assumes PV_SHIM mode. This
If unsure, say N.
+if !PV_SHIM_EXCLUSIVE
+
+config HYPERV_GUEST
+ bool "Hyper-V Guest"
+ select GUEST
+ ---help---
+ Support for Xen detecting when it is running under Hyper-V.
+
+ If unsure, say N.
+
+endif
+
config MEM_SHARING
bool "Xen memory sharing support" if EXPERT = "y"
depends on HVM