From: Justin M. Forbes jforbes@fedoraproject.org
Remove EXPERT from ARCH_FORCE_MAX_ORDER for aarch64
Upstream commit 34affcd7577a232803f729d1870ba475f294e4ea has hidden this behind EXPERT with a very different value (10) than we have been using (13). While I am still making the case to revert this patch upstream, let's at least drop the EXPERT requirement so our current configs will continue to work.
Signed-off-by: Justin M. Forbes jforbes@fedoraproject.org
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index blahblah..blahblah 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -1516,7 +1516,7 @@ config XEN # 16K | 27 | 14 | 13 | 11 | # 64K | 29 | 16 | 13 | 13 | config ARCH_FORCE_MAX_ORDER - int "Order of maximal physically contiguous allocations" if EXPERT && (ARM64_4K_PAGES || ARM64_16K_PAGES) + int "Order of maximal physically contiguous allocations" if ARM64_4K_PAGES || ARM64_16K_PAGES default "13" if ARM64_64K_PAGES default "11" if ARM64_16K_PAGES default "10"
-- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2450
From: Mark Salter on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2450#note_1375471...
There was also an earlier commit 23baf831a32c which changed the meaning of MAX_ORDER. The old MAX_ORDER meant the max alloc order was MAX_ORDER-1, but after 23baf831a32c, the max alloc order is MAX_ORDER. So we also need to change our configs to keep things as they were.
kernel@lists.fedoraproject.org
-
Justin M. Forbes (via Email Bridge) -
Mark Salter (via Email Bridge)