From: sashiko-bot@kernel.org
To: "Chen Pei" <cp0613@linux.alibaba.com>,
pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
rppt@kernel.org, pasha.tatashin@soleen.com, pratyush@kernel.org,
graf@amazon.com, shuah@kernel.org
Cc: guoren@kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v3 1/4] riscv: Call early_ioremap_setup() before parsing the DTB
Date: Sat, 07 Nov 2026 07:15:32 +0000 [thread overview]
Message-ID: <sashiko-outbox-202682@kernel.org> (raw)
In-Reply-To: <20261106071459.2003-2-cp0613@linux.alibaba.com>
> parse_dtb() can reach early_memremap(), whose return value is composed
> from the slot table that early_ioremap_setup() fills in - and on RISC-V
> that setup ran after the scan, so the mapping came back NULL. The DT
> based kexec handover parsing is the first caller to hit this:
> kho_populate() cannot map the handover FDT and the handover is dropped.
>
> Run early_ioremap_setup() before parse_dtb(), as arm64 and x86 already
> do.
>
> Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106071459.2003-1-cp0613@linux.alibaba.com?part=1
next prev parent reply other threads:[~2026-11-07 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 7:14 [PATCH v3 0/4] riscv: Enable kexec handover and live update Chen Pei
2026-11-06 7:14 ` [PATCH v3 1/4] riscv: Call early_ioremap_setup() before parsing the DTB Chen Pei
2026-11-07 7:15 ` sashiko-bot [this message]
2026-11-08 15:24 ` Pasha Tatashin
2026-11-06 7:14 ` [PATCH v3 2/4] riscv: Add support for kexec handover (KHO) Chen Pei
2026-11-07 7:15 ` sashiko-bot
2026-11-07 15:27 ` Chen Pei
2026-11-08 15:24 ` Pasha Tatashin
2026-11-10 9:24 ` Mike Rapoport
2026-11-06 7:14 ` [PATCH v3 3/4] selftests: kho: Add riscv support Chen Pei
2026-11-07 7:15 ` sashiko-bot
2026-11-08 11:16 ` Mike Rapoport
2026-11-08 15:24 ` Pasha Tatashin
2026-11-06 7:14 ` [PATCH v3 4/4] selftests: liveupdate: " Chen Pei
2026-11-07 7:15 ` sashiko-bot
2026-11-08 11:16 ` Mike Rapoport
2026-11-08 15:24 ` Pasha Tatashin
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=sashiko-outbox-202682@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alex@ghiti.fr \
--cc=cp0613@linux.alibaba.com \
--cc=graf@amazon.com \
--cc=guoren@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shuah@kernel.org \
/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