[PATCH 18/18] arm64: Remove user-selectable HVO Kconfig

[James Houghton <jthoughton@google.com>]

The Kconfig is not ideal; it is niche and difficult to understand for
users. The Kconfig was added to avoid the following regression: if HVO
is compiled in and all boot CPUs support it, any late CPUs that do not
will not be onlined.

The implementation now avoids this regression as long as HVO is not
actively in use. Therefore, drop the Kconfig.

Signed-off-by: James Houghton <jthoughton@google.com>
---
 arch/arm64/Kconfig | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index cf4bd6bd7f11..2a59155f68dc 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -259,7 +259,7 @@ config ARM64
 	select USER_STACKTRACE_SUPPORT
 	select VDSO_GETRANDOM
 	select VMAP_STACK
-	select ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP if ARM64_WANT_OPTIMIZE_HUGETLB_VMEMMAP
+	select ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP if ARM64_HW_AFDBM
 	help
 	  ARM 64-bit (AArch64) Linux support.
 
@@ -1608,17 +1608,6 @@ config ARCH_SPARSEMEM_ENABLE
 	def_bool y
 	select SPARSEMEM_VMEMMAP_ENABLE
 
-config ARM64_WANT_OPTIMIZE_HUGETLB_VMEMMAP
-	bool "Enable support for HugeTLB Vmemmap Optimization (HVO)"
-	default n
-	depends on HUGETLB_PAGE && SPARSEMEM_VMEMMAP && ARM64_HW_AFDBM
-	help
-	  Enable support for HVO. When enabled, late-onlining of CPUs that do
-	  not support features required by HVO will not be onlined if all boot
-	  CPUs do have such support.
-
-	  If unsure, say N
-
 config HW_PERF_EVENTS
 	def_bool y
 	depends on ARM_PMU
-- 
2.55.0.795.g602f6c329a-goog