From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Feng Zhou <zhoufeng.zf@bytedance.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Chen Zhou <dingguo.cz@antgroup.com>,
John Donnelly <John.p.donnelly@oracle.com>,
Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: [PATCH v21 5/5] docs: kdump: Update the crashkernel description for arm64
Date: Tue, 15 Mar 2022 19:59:33 +0800 [thread overview]
Message-ID: <YjB/pTWF8wKcATaq@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220227030717.1464-6-thunder.leizhen@huawei.com>
On 02/27/22 at 11:07am, Zhen Lei wrote:
> Now arm64 has added support for "crashkernel=X,high" and
> "crashkernel=Y,low", and implements "crashkernel=X[@offset]" in the
> same way as x86. So update the Documentation.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Looks good to me, thx.
Acked-by: Baoquan He <bhe@redhat.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index f5a27f067db9ed9..63098786c93828c 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -789,7 +789,7 @@
> memory region [offset, offset + size] for that kernel
> image. If '@offset' is omitted, then a suitable offset
> is selected automatically.
> - [KNL, X86-64] Select a region under 4G first, and
> + [KNL, X86-64, ARM64] 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.
> @@ -802,20 +802,20 @@
> Documentation/admin-guide/kdump/kdump.rst for an example.
>
> crashkernel=size[KMG],high
> - [KNL, X86-64] range could be above 4G. Allow kernel
> + [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.
> It will be ignored if crashkernel=X is specified.
> crashkernel=size[KMG],low
> - [KNL, X86-64] range under 4G. When crashkernel=X,high
> + [KNL, X86-64, ARM64] 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
> requires at least 64M+32K low memory, also enough extra
> low memory is needed to make sure DMA buffers for 32-bit
> - devices won't run out. Kernel would try to allocate at
> + devices won't run out. Kernel would try to allocate
> at least 256M below 4G automatically.
> This one let user to specify own low range under 4G
> for second kernel instead.
> --
> 2.25.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-15 12:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 3:07 [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2022-02-27 3:07 ` [PATCH v21 1/5] kdump: return -ENOENT if required cmdline option does not exist Zhen Lei
2022-03-15 11:57 ` Baoquan He
2022-03-15 12:21 ` Baoquan He
2022-03-15 13:32 ` Leizhen (ThunderTown)
2022-03-16 5:17 ` Baoquan He
2022-03-16 5:39 ` Baoquan He
2022-03-16 6:15 ` Leizhen (ThunderTown)
2022-02-27 3:07 ` [PATCH v21 2/5] arm64: Use insert_resource() to simplify code Zhen Lei
2022-02-27 3:07 ` [PATCH v21 3/5] arm64: kdump: reimplement crashkernel=X Zhen Lei
2022-03-16 12:11 ` Baoquan He
2022-03-16 13:11 ` Leizhen (ThunderTown)
2022-03-17 2:36 ` Baoquan He
2022-03-17 3:19 ` Leizhen (ThunderTown)
2022-03-17 3:47 ` Baoquan He
2022-03-17 7:30 ` Leizhen (ThunderTown)
2022-03-17 2:38 ` Baoquan He
2022-03-17 3:23 ` Leizhen (ThunderTown)
2022-03-21 13:29 ` John Donnelly
2022-03-21 14:09 ` Dave Kleikamp
2022-03-22 1:58 ` Leizhen (ThunderTown)
2022-02-27 3:07 ` [PATCH v21 4/5] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2022-02-27 3:07 ` [PATCH v21 5/5] docs: kdump: Update the crashkernel description for arm64 Zhen Lei
2022-03-15 11:59 ` Baoquan He [this message]
2022-04-08 9:32 ` [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump Baoquan He
2022-04-08 9:47 ` Leizhen (ThunderTown)
2022-04-11 2:56 ` Baoquan He
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=YjB/pTWF8wKcATaq@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=John.p.donnelly@oracle.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.kleikamp@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=dingguo.cz@antgroup.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=frowand.list@gmail.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=vgoyal@redhat.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=zhoufeng.zf@bytedance.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;
as well as URLs for NNTP newsgroup(s).