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, shuah@kernel.org
Subject: Re: [PATCH v2 3/5] riscv: Add support for kexec handover (KHO)
Date: Wed, 4 Nov 2026 21:45:47 +0800 [thread overview]
Message-ID: <20261104134550.1779-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <sashiko-outbox-196857@kernel.org>
> As reported by Sashiko on v1 [1], 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?
Both, confirmed by measurement, and neither is riscv code. Mike Rapoport
has a patch that resolves it, so this series carries nothing for it:
https://lore.kernel.org/kexec/20261103-kho-bootmem-sizing-v1-1-45aa74098f34@kernel.org/
Best regards,
Chen
next prev parent reply other threads:[~2026-11-04 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:09 [PATCH v2 0/5] riscv: Enable kexec handover and live update Chen Pei
2026-11-03 8:09 ` [PATCH v2 1/5] kho: Do not translate the handover FDT address in is_kho_boot() Chen Pei
2026-11-05 13:07 ` Mike Rapoport
2026-11-03 8:09 ` [PATCH v2 2/5] riscv: Call early_ioremap_setup() before parsing the DTB Chen Pei
2026-11-03 8:09 ` [PATCH v2 3/5] riscv: Add support for kexec handover (KHO) Chen Pei
2026-11-04 8:10 ` sashiko-bot
2026-11-04 13:45 ` Chen Pei [this message]
2026-11-03 8:09 ` [PATCH v2 4/5] selftests: kho: Add riscv support Chen Pei
2026-11-05 13:08 ` Mike Rapoport
2026-11-03 8:09 ` [PATCH v2 5/5] selftests: liveupdate: " Chen Pei
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=20261104134550.1779-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=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