public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: "chenjiahao (C)" <chenjiahao16@huawei.com>
To: Simon Horman <horms@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<kexec@lists.infradead.org>, <linux-doc@vger.kernel.org>,
	<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<conor.dooley@microchip.com>, <guoren@kernel.org>,
	<heiko@sntech.de>, <bjorn@rivosinc.com>, <alex@ghiti.fr>,
	<akpm@linux-foundation.org>, <atishp@rivosinc.com>,
	<bhe@redhat.com>, <thunder.leizhen@huawei.com>
Subject: Re: [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low]
Date: Mon, 10 Apr 2023 17:20:29 +0800	[thread overview]
Message-ID: <826e8733-2f02-e0db-ee34-a6ae0cadb040@huawei.com> (raw)
In-Reply-To: <ZDAGi2/+1q0oEUZ5@kernel.org>


On 2023/4/7 20:03, Simon Horman wrote:
> On Fri, Apr 07, 2023 at 06:02:05AM +0800, Chen Jiahao wrote:
>> On riscv, the current crash kernel allocation logic is trying to
>> allocate within 32bit addressible memory region by default, if
>> failed, try to allocate without 4G restriction.
>>
>> In need of saving DMA zone memory while allocating a relatively large
>> crash kernel region, allocating the reserved memory top down in
>> high memory, without overlapping the DMA zone, is a mature solution.
>> Here introduce the parameter option crashkernel=X,[high,low].
>>
>> One can reserve the crash kernel from high memory above DMA zone range
>> by explicitly passing "crashkernel=X,high"; or reserve a memory range
>> below 4G with "crashkernel=X,low".
>>
>> Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com>
> ...
>
>> @@ -1180,14 +1206,37 @@ static void __init reserve_crashkernel(void)
>>   		return;
>>   	}
>>   
>> -	ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(),
>> +	ret = parse_crashkernel(cmdline, memblock_phys_mem_size(),
>>   				&crash_size, &crash_base);
>> -	if (ret || !crash_size)
>> +	if (ret == -ENOENT) {
>> +		/*
>> +		 * crashkernel=X,[high,low] can be specified or not, but
>> +		 * invalid value is not allowed.
> nit: Perhaps something like this would be easier to correlate with the
>       code that follows:
>
> 		/* Fallback to crashkernel=X,[high,low] */
>
Agreed, this would be more concise and accurate.
>> +		 */
>> +		ret = parse_crashkernel_high(cmdline, 0, &crash_size, &crash_base);
>> +		if (ret || !crash_size)
>> +			return;
>> +
>> +		/*
>> +		 * crashkernel=Y,low is valid only when crashkernel=X,high
>> +		 * is passed and high memory is reserved successful.
> nit: s/successful/successfully/

I will fix above nits and resend another version later, thanks.


>> +		 */
>> +		ret = parse_crashkernel_low(cmdline, 0, &crash_low_size, &crash_base);
>> +		if (ret == -ENOENT)
>> +			crash_low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE;
>> +		else if (ret)
>> +			return;
>> +
>> +		search_start = search_low_max;
>> +	} else if (ret || !crash_size) {
>> +		/* Invalid argument value specified */
>>   		return;
>> +	}
> ...

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-04-10  9:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 22:02 [PATCH -next v3 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-04-06 22:02 ` [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-04-07  9:06   ` Guo Ren
2023-04-07 12:03     ` Simon Horman
2023-04-11  1:38       ` Guo Ren
2023-04-07 12:03   ` Simon Horman
2023-04-07 12:58     ` Leizhen (ThunderTown)
2023-04-08  2:00       ` Leizhen (ThunderTown)
2023-04-10  9:52         ` chenjiahao (C)
2023-04-10  9:20     ` chenjiahao (C) [this message]
2023-04-06 22:02 ` [PATCH -next v3 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-04-07  8:34   ` Guo Ren
2023-04-07 12:04   ` Simon Horman
2023-04-08  2:01   ` Leizhen (ThunderTown)
2023-04-07 12:05 ` [PATCH -next v3 0/2] support allocating crashkernel above 4G explicitly on riscv Simon Horman
2023-04-10 10:02   ` chenjiahao (C)

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=826e8733-2f02-e0db-ee34-a6ae0cadb040@huawei.com \
    --to=chenjiahao16@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=atishp@rivosinc.com \
    --cc=bhe@redhat.com \
    --cc=bjorn@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=guoren@kernel.org \
    --cc=heiko@sntech.de \
    --cc=horms@kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=thunder.leizhen@huawei.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