From: Mike Rapoport <rppt@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Chen Pei <cp0613@linux.alibaba.com>,
pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
pratyush@kernel.org, graf@amazon.com, shuah@kernel.org,
guoren@kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v3 2/4] riscv: Add support for kexec handover (KHO)
Date: Tue, 10 Nov 2026 11:24:35 +0200 [thread overview]
Message-ID: <avLi0_mYXatBWmpL@kernel.org> (raw)
In-Reply-To: <179415145358.358073.165272378597657083.b4-review@b4>
On Sun, Nov 08, 2026 at 10:24:13AM -0500, Pasha Tatashin wrote:
> > The generic handover paths are already in place on RISC-V: the outgoing
> > kernel publishes the handover FDT and the bootmem list in /chosen of the
> > DTB built by of_kexec_alloc_and_setup_fdt(), and the incoming kernel
> > picks both up while scanning that node. Only the architecture symbol is
> > missing.
> >
> > Set it to 64BIT && MMU: ARCH_SUPPORTS_KEXEC_FILE is already 64BIT only,
> > and KEXEC_HANDOVER selects CMA, which depends on MMU.
> >
> > Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
> >
> > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> > index e7891a2a89da..a5c56252ff44 100644
> > --- a/arch/riscv/Kconfig
> > +++ b/arch/riscv/Kconfig
> > @@ -1125,6 +1125,9 @@ config ARCH_SELECTS_KEXEC_FILE
> > config ARCH_SUPPORTS_KEXEC_PURGATORY
> > def_bool ARCH_SUPPORTS_KEXEC_FILE
> >
> > +config ARCH_SUPPORTS_KEXEC_HANDOVER
> > + def_bool 64BIT && MMU
> > +
> > config ARCH_SUPPORTS_CRASH_DUMP
> > def_bool y
>
> Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
>
> But pre-reqs. should be applied prior taking this series:
>
> 1. https://lore.kernel.org/all/20261023054518.3258350-1-gthelen@google.com
I'm planning to send it to Linus this week.
> 2. https://lore.kernel.org/all/20261104-kho-bootmem-sizing-v2-0-b0d1a834780f@kernel.org
This is easy if we take it via liveupdate tree :)
@ricsv folks, how do you prefer to play it?
> --
> Pasha
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-11-10 9:24 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
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 [this message]
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=avLi0_mYXatBWmpL@kernel.org \
--to=rppt@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=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).