All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] RISC-V: Don't build XIP kernels under allyesconfig
@ 2021-04-23  5:55 ` Palmer Dabbelt
  0 siblings, 0 replies; 2+ messages in thread
From: Palmer Dabbelt @ 2021-04-23  5:55 UTC (permalink / raw)
  To: linux-riscv
  Cc: Paul Walmsley, Palmer Dabbelt, aou, linux-riscv, linux-kernel,
	kernel-team, Palmer Dabbelt

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 --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
-- 
2.31.1.498.g6c1eba8ee3d-goog


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* [PATCH] RISC-V: Don't build XIP kernels under allyesconfig
@ 2021-04-23  5:55 ` Palmer Dabbelt
  0 siblings, 0 replies; 2+ messages in thread
From: Palmer Dabbelt @ 2021-04-23  5:55 UTC (permalink / raw)
  To: linux-riscv
  Cc: Paul Walmsley, Palmer Dabbelt, aou, linux-riscv, linux-kernel,
	kernel-team, Palmer Dabbelt

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 --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
-- 
2.31.1.498.g6c1eba8ee3d-goog


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-04-23  6:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-23  5:55 [PATCH] RISC-V: Don't build XIP kernels under allyesconfig Palmer Dabbelt
2021-04-23  5:55 ` Palmer Dabbelt

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.