From: Chen Pei <cp0613@linux.alibaba.com>
To: sashiko-bot@kernel.org
Cc: alex@ghiti.fr, graf@amazon.com, guoren@kernel.org,
kexec@lists.infradead.org, linux-mm@kvack.org,
palmer@dabbelt.com, pasha.tatashin@soleen.com, pjw@kernel.org,
pratyush@kernel.org, rppt@kernel.org,
sashiko-reviews@lists.linux.dev, shuah@kernel.org
Subject: Re: [PATCH 2/4] riscv: Add support for kexec handover (KHO)
Date: Mon, 26 Oct 2026 17:15:47 +0800 [thread overview]
Message-ID: <20261026091550.9348-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <sashiko-outbox-183678@kernel.org>
> [Severity: High]
> Can enabling ARCH_SUPPORTS_KEXEC_HANDOVER trigger a BUG_ON() in
> linear_mapping_pa_to_va() during efi_init() when booting a KHO kexec
> kernel on a 64-bit RISC-V UEFI system?
Confirmed. Reproduced on qemu virt booting through edk2 with
DEBUG_VIRTUAL enabled and "kho=on" on the outgoing kernel: the first
handover dies in the incoming one during EFI setup, before the console
registers, so it stays silent without an earlycon.
This will be fixed in v2.
> [Severity: Medium]
> Also, will kho_reserve_bootmem() fail on 64-bit RISC-V platforms
> where DRAM starts at or above 4 GiB, or record a 0-byte region when
> all DRAM lies below 4 GiB?
Confirmed, both halves. That is generic KHO code, not the riscv
enablement, so I will send a separate patch for it.
Best regards,
Chen
next prev parent reply other threads:[~2026-10-26 9:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 11:16 [PATCH 0/4] riscv: Enable kexec handover and live update Chen Pei
2026-10-23 11:16 ` Chen Pei
2026-10-23 11:16 ` [PATCH 1/4] riscv: Call early_ioremap_setup() before parsing the DTB Chen Pei
2026-10-23 11:16 ` Chen Pei
2026-10-24 11:16 ` sashiko-bot
2026-10-23 11:16 ` [PATCH 2/4] riscv: Add support for kexec handover (KHO) Chen Pei
2026-10-23 11:16 ` Chen Pei
2026-10-24 11:16 ` sashiko-bot
2026-10-26 9:15 ` Chen Pei [this message]
2026-10-23 11:16 ` [PATCH 3/4] selftests: kho: Add riscv support Chen Pei
2026-10-23 11:16 ` Chen Pei
2026-10-24 11:16 ` sashiko-bot
2026-10-23 11:16 ` [PATCH 4/4] selftests: liveupdate: " Chen Pei
2026-10-23 11:16 ` Chen Pei
2026-10-24 11:16 ` sashiko-bot
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=20261026091550.9348-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=alex@ghiti.fr \
--cc=graf@amazon.com \
--cc=guoren@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sashiko-bot@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 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.