From: Baoquan He <bhe@redhat.com>
To: Chen Jiahao <chenjiahao16@huawei.com>
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, thunder.leizhen@huawei.com,
horms@kernel.org
Subject: Re: [PATCH -next v9 2/2] docs: kdump: Update the crashkernel description for riscv
Date: Wed, 26 Jul 2023 18:25:19 +0800 [thread overview]
Message-ID: <ZMD0jxzH0jmFLTd8@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230726175000.2536220-3-chenjiahao16@huawei.com>
On 07/26/23 at 05:50pm, 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.
Acked-by: Baoquan He <bhe@redhat.com>
>
> Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com>
> Reviewed-by: Guo Ren <guoren@kernel.org>
> Reviewed-by: Simon Horman <horms@kernel.org>
> Reviewed-by: Zhen Lei <thunder.leizhen@huawei.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 a1457995fd41..bd519749968f 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -862,7 +862,7 @@
> memory region [offset, offset + size] for that kernel
> image. If '@offset' 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 '@offset'
> hasn't been specified.
> See Documentation/admin-guide/kdump/kdump.rst for further details.
> @@ -875,14 +875,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
> @@ -893,6 +893,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.
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-26 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 17:49 [PATCH -next v9 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-07-26 17:49 ` [PATCH -next v9 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-07-26 10:24 ` Baoquan He
2023-07-26 17:50 ` [PATCH -next v9 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-07-26 10:25 ` Baoquan He [this message]
2023-08-29 9:54 ` [PATCH -next v9 0/2] support allocating crashkernel above 4G explicitly on riscv chenjiahao (C)
2023-08-30 13:20 ` patchwork-bot+linux-riscv
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=ZMD0jxzH0jmFLTd8@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=atishp@rivosinc.com \
--cc=bjorn@rivosinc.com \
--cc=chenjiahao16@huawei.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