diff mbox series

RISC-V: Don't build XIP kernels under allyesconfig

Message ID 20210423055551.447922-1-palmer@dabbelt.com (mailing list archive)
State New, archived
Headers show
Series RISC-V: Don't build XIP kernels under allyesconfig | expand

Commit Message

Palmer Dabbelt April 23, 2021, 5:55 a.m. UTC 
From: Palmer Dabbelt <palmerdabbelt@google.com>

We have a fixed memory layout for XIP kernels, which means we can't
support very large kernel images.  This is good enough for now, as XIP
users aren't likely to build huge kernels.  It does, however, mean that
allyesconfig breaks which is an issue.

This makes XIP depend on !COMPILE_TEST.  That's a bit of a hack, but
there are some other !COMPILE_TEST dependencies.  This will result in
build bots getting less coverage for XIP, but it's the best I could come
up with.

Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>

---

I've squashed this into the XIP patch, which is on for-next.
---
 arch/riscv/Kconfig | 3 ---
 1 file changed, 3 deletions(-)
diff mbox series

Patch

diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index eec1ede79609..66a03b38d12a 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -508,9 +508,6 @@  config PHYS_RAM_BASE
 config XIP_KERNEL
 	bool "Kernel Execute-In-Place from ROM"
 	depends on MMU && SPARSEMEM
-	# This prevents XIP from being enabled by all{yes,mod}config, which
-	# fail to build since XIP doesn't support large kernels.
-	depends on !COMPILE_TEST
 	select PHYS_RAM_BASE_FIXED
 	help
 	  Execute-In-Place allows the kernel to run from non-volatile storage