From: Baoquan he <bhe@redhat.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>, kexec@lists.infradead.org
Cc: linuxppc-dev@lists.ozlabs.org,
Hari Bathini <hbathini@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Shivang Upadhyay <shivangu@linux.ibm.com>
Subject: Re: [PATCH 0/4] powerpc/kdump: Support high crashkernel reservation
Date: Tue, 28 Oct 2025 14:23:53 +0800 [thread overview]
Message-ID: <aQBheTeMycPuDHJ+@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20251027151338.819957-1-sourabhjain@linux.ibm.com>
Cc kexec mailing list.
On 10/27/25 at 08:43pm, Sourabh Jain wrote:
> Add support for reserving crashkernel memory in higher address ranges
> using the crashkernel=xxM,high command-line option.
>
> With this feature, most of the crashkernel memory for kdump will be
> reserved in high memory regions, while only a small portion (64 MB) will
> be reserved in low memory for the kdump kernel. This helps free up low
> memory for other components that require allocations in that region.
>
> For example, if crashkernel=2G,high is specified, the kernel will reserve
> 2 GB of crashkernel memory near the end of system RAM and an additional
> 64 MB of low memory (below 1 GB) for RTAS to function properly.
>
> Currently, this feature is supported only on PPC64 systems with 64-bit
> RTAS instantiation and Radix MMU enabled.
>
> Two critical changes were made to support this feature:
>
> - CPU feature discovery is now performed before crashkernel
> reservation. This ensures the MMU type is determined before reserving
> crashkernel memory. (Patch 01/04)
>
> - RTAS instantiation has been moved to 64-bit mode. (Patch 02/04)
>
> Apply the following patch first, and then apply this patch series:
> https://lore.kernel.org/all/20251024170118.297472-1-sourabhjain@linux.ibm.com/
>
> Cc: Baoquan he <bhe@redhat.com>
> Cc: Hari Bathini <hbathini@linux.ibm.com>
> Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
> Cc: Shivang Upadhyay <shivangu@linux.ibm.com>
>
> Sourabh Jain (4):
> powerpc/mmu: do MMU type discovery before crashkernel reservation
> powerpc: move to 64-bit RTAS
> powerpc/kdump: consider high crashkernel memory if enabled
> powerpc/kdump: add support for high crashkernel reservation
>
> arch/powerpc/include/asm/book3s/64/mmu.h | 1 +
> arch/powerpc/include/asm/crash_reserve.h | 8 +++++
> arch/powerpc/include/asm/kexec.h | 1 +
> arch/powerpc/include/asm/mmu.h | 1 +
> arch/powerpc/include/asm/rtas.h | 11 ++++++
> arch/powerpc/kernel/prom.c | 28 ++++++++-------
> arch/powerpc/kernel/prom_init.c | 26 +++++++++++---
> arch/powerpc/kernel/rtas.c | 5 +++
> arch/powerpc/kernel/rtas_entry.S | 17 ++++++++-
> arch/powerpc/kexec/core.c | 45 +++++++++++++++++-------
> arch/powerpc/kexec/elf_64.c | 10 ++++--
> arch/powerpc/kexec/file_load_64.c | 5 +--
> arch/powerpc/kexec/ranges.c | 24 +++++++++++--
> arch/powerpc/mm/init_64.c | 27 ++++++++------
> 14 files changed, 161 insertions(+), 48 deletions(-)
>
> --
> 2.51.0
>
prev parent reply other threads:[~2025-10-28 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 15:13 [PATCH 0/4] powerpc/kdump: Support high crashkernel reservation Sourabh Jain
2025-10-27 15:13 ` [PATCH 1/4] powerpc/mmu: do MMU type discovery before " Sourabh Jain
2025-10-31 4:53 ` Ritesh Harjani
2025-10-27 15:13 ` [PATCH 2/4] powerpc: move to 64-bit RTAS Sourabh Jain
2025-10-29 12:52 ` Sourabh Jain
2025-10-27 15:13 ` [PATCH 3/4] powerpc/kdump: consider high crashkernel memory if enabled Sourabh Jain
2025-10-27 15:13 ` [PATCH 4/4] powerpc/kdump: add support for high crashkernel reservation Sourabh Jain
2025-10-28 6:23 ` Baoquan he [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=aQBheTeMycPuDHJ+@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=ritesh.list@gmail.com \
--cc=shivangu@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
/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.