From: Palmer Dabbelt <palmer@dabbelt.com> To: linux-riscv@lists.infradead.org Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, kernel-team@android.com, Palmer Dabbelt <palmerdabbelt@google.com> Subject: [PATCH] RISC-V: Don't build XIP kernels under allyesconfig Date: Thu, 22 Apr 2021 22:55:51 -0700 [thread overview] Message-ID: <20210423055551.447922-1-palmer@dabbelt.com> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@dabbelt.com> To: linux-riscv@lists.infradead.org Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, kernel-team@android.com, Palmer Dabbelt <palmerdabbelt@google.com> Subject: [PATCH] RISC-V: Don't build XIP kernels under allyesconfig Date: Thu, 22 Apr 2021 22:55:51 -0700 [thread overview] Message-ID: <20210423055551.447922-1-palmer@dabbelt.com> (raw) 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
next reply other threads:[~2021-04-23 5:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-23 5:55 Palmer Dabbelt [this message] 2021-04-23 5:55 ` [PATCH] RISC-V: Don't build XIP kernels under allyesconfig Palmer Dabbelt
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210423055551.447922-1-palmer@dabbelt.com \ --to=palmer@dabbelt.com \ --cc=aou@eecs.berkeley.edu \ --cc=kernel-team@android.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmerdabbelt@google.com \ --cc=paul.walmsley@sifive.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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.