LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
	mpe@ellerman.id.au
Cc: npiggin@gmail.com, chleroy@kernel.org, ritesh.list@gmail.com,
	shivangu@linux.ibm.com, mahesh@linux.ibm.com,
	adityag@linux.ibm.com, venkat88@linux.ibm.com
Subject: Re: [PATCH v2 4/4] powerpc/kdump: add support for high crashkernel reservation
Date: Mon, 3 Aug 2026 09:40:38 +0530	[thread overview]
Message-ID: <ef4635e2-6971-4125-99c3-a96e2f5a9d10@linux.ibm.com> (raw)
In-Reply-To: <ffd8a15f-9526-413d-8a0e-f86b4b6964b8@linux.ibm.com>



On 26/07/26 16:53, Hari Bathini wrote:
>
>
> On 08/07/26 8:03 pm, Sourabh Jain wrote:
>> With this changes included crashkernel=xxM,high will be supported on
>> powerpc. This allow user to allocated crashkernel memory on higer memory
>> region and keeping the low memory allocation minimal.
>>
>> The low memory reservation is by default set to 64 MB and it is reserved
>> below RTAS_INSTANTIATE_MAX (1G) to make sure rtas instantiation work
>> properly.
>>
>> powerpc uses generic crashkernel parser and reserve functions and they
>> are capable of handling high crashkernel reservtion so
>> arch_reserve_crashkernel() is updated call generic crashkernel praser
>> and reserve function with resptive options to make
>> crashkernel=XXM,high prase and make crashkernel memory get reserved on
>> higher memory regions.
>>
>> Note: High crashkernel is supported only on PPC 64-bit systems when
>> 64-bit RTAS is instantiated and Radix MMU is enabled; otherwise, the
>> crashkernel reservation falls back to the default, even if the kernel
>> command includes crashkernel=XXM,high.
>>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>>   arch/powerpc/include/asm/crash_reserve.h |  6 ++++
>>   arch/powerpc/include/asm/kexec.h         |  1 +
>>   arch/powerpc/include/asm/rtas.h          |  9 +++++
>>   arch/powerpc/kexec/core.c                | 45 +++++++++++++++++-------
>>   4 files changed, 49 insertions(+), 12 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/crash_reserve.h 
>> b/arch/powerpc/include/asm/crash_reserve.h
>> index d1b570ddbf98..4f2096984736 100644
>> --- a/arch/powerpc/include/asm/crash_reserve.h
>> +++ b/arch/powerpc/include/asm/crash_reserve.h
>> @@ -2,6 +2,8 @@
>>   #ifndef _ASM_POWERPC_CRASH_RESERVE_H
>>   #define _ASM_POWERPC_CRASH_RESERVE_H
>>   +#include <asm/rtas.h>
>> +
>>   /* crash kernel regions are Page size agliged */
>>   #define CRASH_ALIGN             PAGE_SIZE
>>   @@ -12,5 +14,9 @@ static inline bool arch_add_crash_res_to_iomem(void)
>>   }
>>   #define arch_add_crash_res_to_iomem arch_add_crash_res_to_iomem
>>   #endif
>> +#define DEFAULT_CRASH_KERNEL_LOW_SIZE SZ_64M
>> +
>> +#define CRASH_ADDR_LOW_MAX    RTAS_INSTANTIATE_MAX
>> +#define CRASH_ADDR_HIGH_MAX    memblock_end_of_DRAM()
>>     #endif /* _ASM_POWERPC_CRASH_RESERVE_H */
>> diff --git a/arch/powerpc/include/asm/kexec.h 
>> b/arch/powerpc/include/asm/kexec.h
>> index e02710d6a2e1..9e676bd3bf03 100644
>> --- a/arch/powerpc/include/asm/kexec.h
>> +++ b/arch/powerpc/include/asm/kexec.h
>> @@ -118,6 +118,7 @@ int setup_new_fdt_ppc64(const struct kimage 
>> *image, void *fdt, struct crash_mem
>>   int __init overlaps_crashkernel(unsigned long start, unsigned long 
>> size);
>>   extern void arch_reserve_crashkernel(void);
>>   extern void kdump_cma_reserve(void);
>> +unsigned long long __init get_crash_base(unsigned long long 
>> crash_base);
>>   #else
>>   static inline void arch_reserve_crashkernel(void) {}
>>   static inline int overlaps_crashkernel(unsigned long start, 
>> unsigned long size) { return 0; }
>> diff --git a/arch/powerpc/include/asm/rtas.h 
>> b/arch/powerpc/include/asm/rtas.h
>> index aaa4c3bc1d61..d290437d8131 100644
>> --- a/arch/powerpc/include/asm/rtas.h
>> +++ b/arch/powerpc/include/asm/rtas.h
>> @@ -561,6 +561,14 @@ static inline int page_is_rtas_user_buf(unsigned 
>> long pfn)
>>       return 0;
>>   }
>>   +static inline bool is_rtas_high_crashkernel_capable(void)
>> +{
>> +    if (rtas_64)
>> +        return true;
>> +
>> +    return false;
>> +}
>> +
>>   /* Not the best place to put pSeries_coalesce_init, will be fixed 
>> when we
>>    * move some of the rtas suspend-me stuff to pseries */
>>   void pSeries_coalesce_init(void);
>> @@ -569,6 +577,7 @@ void rtas_initialize(void);
>>   static inline int page_is_rtas_user_buf(unsigned long pfn) { return 
>> 0;}
>>   static inline void pSeries_coalesce_init(void) { }
>>   static inline void rtas_initialize(void) { }
>
>> +static inline bool is_rtas_high_crashkernel_capable(void) { return 
>> true; }
>
> Though !CONFIG_PPC_RTAS may imply radix MMU and high crashkernel
> capable, is_rtas_high_crashkernel_capable() returning true for
> !CONFIG_PPC_RTAS case seems counter-intuitive.
>
>>   #endif
>>     #ifdef CONFIG_HV_PERF_CTRS
>> diff --git a/arch/powerpc/kexec/core.c b/arch/powerpc/kexec/core.c
>> index dc44f11be353..81fc437377c8 100644
>> --- a/arch/powerpc/kexec/core.c
>> +++ b/arch/powerpc/kexec/core.c
>> @@ -15,6 +15,7 @@
>>   #include <linux/irq.h>
>>   #include <linux/ftrace.h>
>>   +#include <asm/rtas.h>
>>   #include <asm/kdump.h>
>>   #include <asm/machdep.h>
>>   #include <asm/pgalloc.h>
>> @@ -64,7 +65,7 @@ void machine_kexec(struct kimage *image)
>>     static unsigned long long crashk_cma_size;
>>   -static unsigned long long __init get_crash_base(unsigned long long 
>> crash_base)
>> +unsigned long long __init get_crash_base(unsigned long long crash_base)
>>   {
>>     #ifndef CONFIG_NONSTATIC_KERNEL
>> @@ -104,35 +105,55 @@ static unsigned long long __init 
>> get_crash_base(unsigned long long crash_base)
>>   #endif
>>   }
>
>> +static bool high_crashkernel_supported(void)
>> +{
>> +#if defined(CONFIG_PPC64) && (defined(CONFIG_PPC_PSERIES) || 
>> defined(CONFIG_PPC_POWERNV))
>> +    if (early_radix_enabled() && is_rtas_high_crashkernel_capable())
>> +        return true;
>> +#endif
>> +    return false;
>> +}
>
> Have this function that accounts for high crashkernel support in
> different scenarios and drop is_rtas_high_crashkernel_capable()? 

Agree.

- Sourabh Jain



      reply	other threads:[~2026-08-03  4:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 14:33 [PATCH v2 0/4] powerpc/kdump: Support high crashkernel reservation Sourabh Jain
2026-07-08 14:33 ` [PATCH v2 1/4] powerpc/mmu: do MMU type discovery before " Sourabh Jain
2026-07-10  2:44   ` Ritesh Harjani
2026-07-13 13:12     ` Sourabh Jain
2026-07-26 10:54   ` Hari Bathini
2026-08-03  3:45     ` Sourabh Jain
2026-07-08 14:33 ` [PATCH v2 2/4] powerpc: move to 64-bit RTAS Sourabh Jain
2026-07-26 10:55   ` Hari Bathini
2026-08-03  3:56     ` Sourabh Jain
2026-07-08 14:33 ` [PATCH v2 3/4] powerpc/kdump: consider high crashkernel memory if enabled Sourabh Jain
2026-07-08 14:33 ` [PATCH v2 4/4] powerpc/kdump: add support for high crashkernel reservation Sourabh Jain
2026-07-26 10:56   ` Hari Bathini
2026-08-03  4:09     ` Sourabh Jain
2026-07-26 11:23   ` Hari Bathini
2026-08-03  4:10     ` Sourabh Jain [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=ef4635e2-6971-4125-99c3-a96e2f5a9d10@linux.ibm.com \
    --to=sourabhjain@linux.ibm.com \
    --cc=adityag@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=hbathini@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=ritesh.list@gmail.com \
    --cc=shivangu@linux.ibm.com \
    --cc=venkat88@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox