From: Catalin Marinas <catalin.marinas@arm.com>
To: Baoquan He <bhe@redhat.com>
Cc: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>,
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, 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 v24 6/6] docs: kdump: Update the crashkernel description for arm64
Date: Sat, 7 May 2022 19:22:57 +0100 [thread overview]
Message-ID: <Yna5AVli1IIUd2kg@arm.com> (raw)
In-Reply-To: <YnXn87JnfUxI2lC2@MiWiFi-R3L-srv>
On Sat, May 07, 2022 at 11:30:59AM +0800, Baoquan He wrote:
> On 05/07/22 at 09:41am, Leizhen (ThunderTown) wrote:
> > On 2022/5/7 7:14, Baoquan He wrote:
> > > On 05/06/22 at 07:44pm, Zhen Lei wrote:
> > >> Now arm64 has added support for "crashkernel=X,high" and
> > >> "crashkernel=Y,low". Unlike x86, crash low memory is not allocated if
> > >> "crashkernel=Y,low" is not specified.
> > >>
> > >> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> > >> ---
> > >> Documentation/admin-guide/kernel-parameters.txt | 9 +++++++--
> > >> 1 file changed, 7 insertions(+), 2 deletions(-)
> > >>
> > >> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > >> index 3f1cc5e317ed4a5..aa44c61114aa4b8 100644
> > >> --- a/Documentation/admin-guide/kernel-parameters.txt
> > >> +++ b/Documentation/admin-guide/kernel-parameters.txt
> > >> @@ -808,7 +808,7 @@
> > >> 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
> > >> @@ -821,7 +821,7 @@
> > >> 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.
> > >> @@ -829,6 +829,11 @@
> > >> It will be ignored when crashkernel=X,high is not used
> > >> or memory reserved is below 4G.
> > >>
> > >> + [KNL, ARM64] range in low memory.
> > >> + This one let user to specify a low range in DMA zone for
> > > ^ not needed,
> > > Maybe Catalin can fix it when merging.
> >
> > Delete "This one let user to" or the entire sentence? I understand it to be the former.
>
> Oh, I mean the 'to' is not needed. "This one let user specify ....". The
> 'to' is a grammer mistake.
Slightly more correct is "This one lets the user specify..."
I can fix them up when applying.
--
Catalin
_______________________________________________
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-05-07 18:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 11:43 [PATCH v24 0/6] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2022-05-06 11:43 ` [PATCH v24 1/6] kdump: return -ENOENT if required cmdline option does not exist Zhen Lei
2022-05-06 11:43 ` [PATCH v24 2/6] arm64: Use insert_resource() to simplify code Zhen Lei
2022-05-06 11:43 ` [PATCH v24 3/6] arm64: kdump: Reimplement crashkernel=X Zhen Lei
2022-05-06 23:10 ` Baoquan He
2022-05-07 1:34 ` Leizhen (ThunderTown)
2022-05-07 2:07 ` Baoquan He
2022-05-07 3:37 ` Leizhen (ThunderTown)
2022-05-07 9:35 ` Leizhen (ThunderTown)
2022-05-07 11:49 ` Leizhen (ThunderTown)
2022-05-07 12:20 ` Leizhen (ThunderTown)
2022-05-07 13:22 ` Baoquan He
2022-05-07 17:30 ` John Donnelly
2022-05-07 18:50 ` Catalin Marinas
2022-05-09 4:04 ` Baoquan He
2022-05-06 11:44 ` [PATCH v24 4/6] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2022-05-06 23:15 ` [PATCH v24 4/6] of: fdt: Add memory for devices by DT property "linux,usable-memory-range" Baoquan He
2022-05-06 11:44 ` [PATCH v24 5/6] of: Support more than one crash kernel regions for kexec -s Zhen Lei
2022-05-06 23:17 ` Baoquan He
2022-05-07 1:42 ` Leizhen (ThunderTown)
2022-05-07 2:36 ` Baoquan He
2022-05-06 11:44 ` [PATCH v24 6/6] docs: kdump: Update the crashkernel description for arm64 Zhen Lei
2022-05-06 23:14 ` Baoquan He
2022-05-07 1:41 ` Leizhen (ThunderTown)
2022-05-07 3:23 ` Leizhen (ThunderTown)
2022-05-07 3:30 ` Baoquan He
2022-05-07 18:22 ` Catalin Marinas [this message]
2022-05-09 4:05 ` Baoquan He
2022-05-07 19:12 ` [PATCH v24 0/6] support reserving crashkernel above 4G on arm64 kdump Catalin Marinas
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=Yna5AVli1IIUd2kg@arm.com \
--to=catalin.marinas@arm.com \
--cc=John.p.donnelly@oracle.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--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).