From: Chen Pei <cp0613@linux.alibaba.com>
To: pjw@kernel.org
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 0/4] riscv: Enable kexec handover and live update
Date: Mon, 9 Nov 2026 20:28:20 +0800 [thread overview]
Message-ID: <20261109122823.992-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <20261106071459.2003-1-cp0613@linux.alibaba.com>
Hi Paul, could you review this series when you get a chance?
RISC-V needs no architecture-specific code for kexec handover: the
generic paths already work on riscv64, and what this series adds are the
enables. Patch 1 moves early_ioremap_setup() before parse_dtb(), the
order arm64 and x86 already use, because DT-based handover is the first
caller to map memory that early. Patch 2 adds
ARCH_SUPPORTS_KEXEC_HANDOVER. Patches 3 and 4 teach the KHO and live
update vmtest runners about riscv64.
The two prerequisites the series depends on are basically resolved: Greg
Thelen's fix to is_kho_boot() [1] is applied in the liveupdate fixes
tree, and Mike Rapoport's bootmem sizing series [2] is reviewed.
[1] https://lore.kernel.org/all/20261023054518.3258350-1-gthelen@google.com/
[2] https://lore.kernel.org/kexec/20261104-kho-bootmem-sizing-v2-0-b0d1a834780f@kernel.org/
Best regards,
Chen
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-11-09 12:28 UTC|newest]
Thread overview: 30+ 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 ` Chen Pei
2026-11-06 7:14 ` [PATCH v3 1/4] riscv: Call early_ioremap_setup() before parsing the DTB Chen Pei
2026-11-06 7:14 ` Chen Pei
2026-11-07 7:15 ` sashiko-bot
2026-11-08 15:24 ` Pasha Tatashin
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-06 7:14 ` 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-08 15:24 ` Pasha Tatashin
2026-11-10 9:24 ` Mike Rapoport
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-06 7:14 ` Chen Pei
2026-11-07 7:15 ` sashiko-bot
2026-11-08 11:16 ` Mike Rapoport
2026-11-08 11:16 ` Mike Rapoport
2026-11-08 15:24 ` Pasha Tatashin
2026-11-08 15:24 ` Pasha Tatashin
2026-11-06 7:14 ` [PATCH v3 4/4] selftests: liveupdate: " Chen Pei
2026-11-06 7:14 ` Chen Pei
2026-11-07 7:15 ` sashiko-bot
2026-11-08 11:16 ` Mike Rapoport
2026-11-08 11:16 ` Mike Rapoport
2026-11-08 15:24 ` Pasha Tatashin
2026-11-08 15:24 ` Pasha Tatashin
2026-11-09 12:28 ` Chen Pei [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=20261109122823.992-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=linux-riscv@lists.infradead.org \
--cc=pjw@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.