[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH] Call SetVirtualAddressMap() by default
To quote Andrew Cooper: > I know we've had this argument before, but not calling > SetVirtualAddressMap() isn't a viable option. It's a prerequisite to > function on literally millions of devices Qubes OS has been shipping EFI_SET_VIRTUAL_ADDRESS_MAP for years, and I believe OpenXT and EVE ship it as well. Mark EFI_SET_VIRTUAL_ADDRESS_MAP as SUPPORTED and enable it by default. Signed-off-by: Demi Marie Obenour <demi@xxxxxxxxxxxxxxxxxxxxxx> --- What is necessary for this patch to be accepted? xen/common/Kconfig | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/xen/common/Kconfig b/xen/common/Kconfig index f1ea3199c8ebdc1e9d0968b9de007f4df44bac79..5b8edb6d81a1296969f968702c5e7f2c775ceba9 100644 --- a/xen/common/Kconfig +++ b/xen/common/Kconfig @@ -215,14 +215,15 @@ config KEXEC If unsure, say Y. config EFI_SET_VIRTUAL_ADDRESS_MAP - bool "EFI: call SetVirtualAddressMap()" if EXPERT + bool "EFI: call SetVirtualAddressMap()" + default y ---help--- Call EFI SetVirtualAddressMap() runtime service to setup memory map for further runtime services. According to UEFI spec, it isn't strictly necessary, but many UEFI implementations misbehave when this call is missing. - If unsure, say N. + If unsure, say Y. config XENOPROF def_bool y -- Sincerely, Demi Marie Obenour (she/her/hers) Invisible Things Lab
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |