From: Pnina Feder <pnina.feder@mobileye.com>
To: bjorn@kernel.org
Cc: alex@ghiti.fr, bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, mick@ics.forth.gr,
palmer@dabbelt.com, paul.walmsley@sifive.com,
Pnina Feder <pnina.feder@mobileye.com>
Subject: [PATCH 1/1] riscv: Change memblock reserved name to be recognized on kexec
Date: Mon, 30 Jun 2025 14:21:30 +0300 [thread overview]
Message-ID: <20250630112309.97162-4-pnina.feder@mobileye.com> (raw)
In-Reply-To: <20250409182129.634415-1-bjorn@kernel.org>
memblock resreved exposes as Reserved on iomem,
kexec tool doesn't take those parts to vmcore, but
the kernel use those address and it needed when opening the vmcore.
Without this fix the crash-tool fails.
Fixes: e94eb7ea6f20 ("riscv: Properly export reserved regions in /proc/iomem")
Signed-off-by: Pnina Feder <pnina.feder@mobileye.com>
---
arch/riscv/kernel/setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c
index 14888e5ea19a..16e0cebed170 100644
--- a/arch/riscv/kernel/setup.c
+++ b/arch/riscv/kernel/setup.c
@@ -249,7 +249,7 @@ static int __init reserve_memblock_reserved_regions(void)
if (start > mem->end || end < mem->start)
continue;
- reserve_region_with_split(mem, start, end, "Reserved");
+ reserve_region_with_split(mem, start, end, "Reserved-memblock");
}
}
--
2.43.0
prev parent reply other threads:[~2025-06-30 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 18:21 [PATCH fixes] riscv: Properly export reserved regions in /proc/iomem Björn Töpel
2025-04-11 10:28 ` Alexandre Ghiti
2025-04-16 18:42 ` patchwork-bot+linux-riscv
2025-06-30 11:21 ` [PATCH 0/1] Fix for riscv vmcore issue Pnina Feder
2025-06-30 13:33 ` Björn Töpel
2025-07-03 12:06 ` Pnina Feder
2025-07-04 12:25 ` Alexandre Ghiti
2025-07-06 13:57 ` Pnina Feder
2025-07-14 12:00 ` Pnina Feder
2025-07-16 6:58 ` Alexandre Ghiti
2025-07-16 11:05 ` Pnina Feder
2025-07-16 11:47 ` Alexandre Ghiti
2025-07-16 18:16 ` Nick Kossifidis
2025-06-30 11:21 ` Pnina Feder [this message]
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=20250630112309.97162-4-pnina.feder@mobileye.com \
--to=pnina.feder@mobileye.com \
--cc=alex@ghiti.fr \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--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
all inboxes | Powered by JetHome®