All of 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
Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 2/2] fadump: reserve param area if below boot_mem_top
Date: Tue, 5 Nov 2024 08:19:44 +0530	[thread overview]
Message-ID: <f4def3a5-727e-4eff-95cd-ece99d133ca5@linux.ibm.com> (raw)
In-Reply-To: <b7350dd0-b835-42fe-8970-da5b0ce16ba6@linux.ibm.com>

Hello Hari,


On 04/11/24 15:50, Hari Bathini wrote:
>
>
> On 04/11/24 2:05 pm, Sourabh Jain wrote:
>> The param area is a memory region where the kernel places additional
>> command-line arguments for fadump kernel. Currently, the param memory
>> area is reserved in fadump kernel if it is above boot_mem_top. However,
>> it should be reserved if it is below boot_mem_top because the fadump
>> kernel already reserves memory from boot_mem_top to the end of DRAM.
>>
>> Currently, there is no impact from not reserving param memory if it is
>> below boot_mem_top, as it is not used after the early boot phase of the
>> fadump kernel. However, if this changes in the future, it could lead t
>> issues in the fadump kernel.
>>
>
> Looks good to me.
>
> Acked-by: Hari Bathini <hbathini@linux.ibm.com>

Thanks for Ack.


- Sourabh Jain

>
>> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>>   arch/powerpc/kernel/fadump.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
>> index 4a3f80f42118..35a8a107e16b 100644
>> --- a/arch/powerpc/kernel/fadump.c
>> +++ b/arch/powerpc/kernel/fadump.c
>> @@ -143,7 +143,7 @@ void __init fadump_append_bootargs(void)
>>       if (!fw_dump.dump_active || !fw_dump.param_area_supported || 
>> !fw_dump.param_area)
>>           return;
>>   -    if (fw_dump.param_area >= fw_dump.boot_mem_top) {
>> +    if (fw_dump.param_area < fw_dump.boot_mem_top) {
>>           if (memblock_reserve(fw_dump.param_area, COMMAND_LINE_SIZE)) {
>>               pr_warn("WARNING: Can't use additional parameters 
>> area!\n");
>>               fw_dump.param_area = 0;
>



  reply	other threads:[~2024-11-05  2:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  8:35 [PATCH 1/2] powerpc/fadump: allocate memory for additional parameters early Sourabh Jain
2024-11-04  8:35 ` [PATCH 2/2] fadump: reserve param area if below boot_mem_top Sourabh Jain
2024-11-04 10:20   ` Hari Bathini
2024-11-05  2:49     ` Sourabh Jain [this message]
2024-11-05  8:16 ` [PATCH 1/2] powerpc/fadump: allocate memory for additional parameters early Michael Ellerman
2024-11-05  8:23   ` Hari Bathini
2024-11-06 12:38   ` Sourabh Jain

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=f4def3a5-727e-4eff-95cd-ece99d133ca5@linux.ibm.com \
    --to=sourabhjain@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    /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.