From: Jisheng Zhang <jszhang@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Atish Patra <atishp@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] riscv: head: use 0 as the default text_offset
Date: Mon, 28 Nov 2022 23:24:42 +0800 [thread overview]
Message-ID: <20221128152442.3403-1-jszhang@kernel.org> (raw)
Commit 0f327f2aaad6 ("RISC-V: Add an Image header that boot loader can
parse.") adds an image header which "is based on ARM64 boot image
header and provides an opportunity to combine both ARM64 & RISC-V
image headers in future.". At that time, arm64's default text_offset
is 0x80000, this is to give "512 KB of guaranteed BSS space to put
the swapper page tables" as commit cfa7ede20f13 ("arm64: set TEXT_OFFSET
to 0x0 in preparation for removing it entirely") pointed out, but
riscv doesn't need the space, so use 0 as the default text_offset.
Before this patch, booting linux kernel on Sipeed bl808 M1s Dock
with u-boot booti cmd:
[ 0.000000] OF: fdt: Ignoring memory range 0x50000000 - 0x50200000
...
[ 0.000000] DMA32 [mem 0x0000000050200000-0x0000000053ffffff]
As can be seen, 2MB DDR(0x50000000 - 0x501fffff) can't be used by
linux.
After this patch, the 64MB DDR is fully usable by linux
[ 0.000000] DMA32 [mem 0x0000000050000000-0x0000000053ffffff]
Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
---
arch/riscv/kernel/head.S | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/arch/riscv/kernel/head.S b/arch/riscv/kernel/head.S
index b865046e4dbb..ef95943f7a70 100644
--- a/arch/riscv/kernel/head.S
+++ b/arch/riscv/kernel/head.S
@@ -38,18 +38,8 @@ ENTRY(_start)
.word 0
#endif
.balign 8
-#ifdef CONFIG_RISCV_M_MODE
- /* Image load offset (0MB) from start of RAM for M-mode */
+ /* Image load offset (0MB) from start of RAM */
.dword 0
-#else
-#if __riscv_xlen == 64
- /* Image load offset(2MB) from start of RAM */
- .dword 0x200000
-#else
- /* Image load offset(4MB) from start of RAM */
- .dword 0x400000
-#endif
-#endif
/* Effective size of kernel image */
.dword _end - _start
.dword __HEAD_FLAGS
--
2.37.2
next reply other threads:[~2022-11-28 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 15:24 Jisheng Zhang [this message]
2022-11-28 16:03 ` [PATCH] riscv: head: use 0 as the default text_offset Andreas Schwab
2022-11-28 20:11 ` Atish Kumar Patra
2022-11-29 5:04 ` Samuel Holland
2022-11-29 5:33 ` Alexandre Ghiti
2022-11-29 6:19 ` Palmer Dabbelt
2022-11-29 6:55 ` Samuel Holland
2022-11-29 9:15 ` Atish Kumar Patra
2022-11-29 18:33 ` Palmer Dabbelt
2022-11-29 9:18 ` Anup Patel
2022-11-29 15:07 ` Jisheng Zhang
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=20221128152442.3403-1-jszhang@kernel.org \
--to=jszhang@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).