[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca1b1ca8-96eb-cdef-5526-6edeaf3ca343@huawei.com>
Date: Sat, 8 Apr 2023 10:01:28 +0800
From: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
To: Chen Jiahao <chenjiahao16@...wei.com>,
<linux-kernel@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
<kexec@...ts.infradead.org>, <linux-doc@...r.kernel.org>
CC: <paul.walmsley@...ive.com>, <palmer@...belt.com>,
<conor.dooley@...rochip.com>, <guoren@...nel.org>,
<heiko@...ech.de>, <bjorn@...osinc.com>, <alex@...ti.fr>,
<akpm@...ux-foundation.org>, <atishp@...osinc.com>,
<bhe@...hat.com>, <horms@...nel.org>
Subject: Re: [PATCH -next v3 2/2] docs: kdump: Update the crashkernel
description for riscv
On 2023/4/7 6:02, Chen Jiahao wrote:
> Now "crashkernel=" parameter on riscv has been updated to support
> crashkernel=X,[high,low]. Through which we can reserve memory region
> above/within 32bit addressible DMA zone.
>
> Here update the parameter description accordingly.
Reviewed-by: Zhen Lei <thunder.leizhen@...wei.com>
>
> Signed-off-by: Chen Jiahao <chenjiahao16@...wei.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 54702bd488eb..41865aae9eaa 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -866,7 +866,7 @@
> memory region [offset, offset + size] for that kernel
> image. If '@...set' is omitted, then a suitable offset
> is selected automatically.
> - [KNL, X86-64, ARM64] Select a region under 4G first, and
> + [KNL, X86-64, ARM64, RISCV] Select a region under 4G first, and
> fall back to reserve region above 4G when '@...set'
> hasn't been specified.
> See Documentation/admin-guide/kdump/kdump.rst for further details.
> @@ -879,14 +879,14 @@
> Documentation/admin-guide/kdump/kdump.rst for an example.
>
> crashkernel=size[KMG],high
> - [KNL, X86-64, ARM64] range could be above 4G. Allow kernel
> - to allocate physical memory region from top, so could
> - be above 4G if system have more than 4G ram installed.
> - Otherwise memory region will be allocated below 4G, if
> - available.
> + [KNL, X86-64, ARM64, RISCV] range could be above 4G.
> + Allow kernel to allocate physical memory region from top,
> + so could be above 4G if system have more than 4G ram
> + installed. Otherwise memory region will be allocated
> + below 4G, if available.
> It will be ignored if crashkernel=X is specified.
> crashkernel=size[KMG],low
> - [KNL, X86-64, ARM64] range under 4G. When crashkernel=X,high
> + [KNL, X86-64, ARM64, RISCV] range under 4G. When crashkernel=X,high
> is passed, kernel could allocate physical memory region
> above 4G, that cause second kernel crash on system
> that require some amount of low memory, e.g. swiotlb
> @@ -897,6 +897,7 @@
> size is platform dependent.
> --> x86: max(swiotlb_size_or_default() + 8MiB, 256MiB)
> --> arm64: 128MiB
> + --> riscv: 128MiB
> This one lets the user specify own low range under 4G
> for second kernel instead.
> 0: to disable low allocation.
>
--
Regards,
Zhen Lei
Powered by blists - more mailing lists