From: Will Deacon <will@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Zhen Lei <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>,
Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
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>,
Chen Zhou <dingguo.cz@antgroup.com>,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v17 00/10] support reserving crashkernel above 4G on arm64 kdump
Date: Mon, 13 Dec 2021 18:50:55 +0000 [thread overview]
Message-ID: <20211213185054.GH12405@willie-the-truck> (raw)
In-Reply-To: <afde1574-23b6-a36a-445e-5fb03873fe86@huawei.com>
On Fri, Dec 10, 2021 at 03:15:00PM +0800, Kefeng Wang wrote:
>
> On 2021/12/10 14:55, Zhen Lei wrote:
> > There are following issues in arm64 kdump:
> > 1. We use crashkernel=X to reserve crashkernel below 4G, which
> > will fail when there is no enough low memory.
> > 2. If reserving crashkernel above 4G, in this case, crash dump
> > kernel will boot failure because there is no low memory available
> > for allocation.
> >
> > To solve these issues, change the behavior of crashkernel=X.
> > crashkernel=X tries low allocation in DMA zone and fall back to high
> > allocation if it fails.
> >
> > We can also use "crashkernel=X,high" to select a high region above
> > DMA zone, which also tries to allocate at least 256M low memory in
> > DMA zone automatically and "crashkernel=Y,low" can be used to allocate
> > specified size low memory.
> >
> > When reserving crashkernel in high memory, some low memory is reserved
> > for crash dump kernel devices. So there may be two regions reserved for
> > crash dump kernel.
> > In order to distinct from the high region and make no effect to the use
> > of existing kexec-tools, rename the low region as "Crash kernel (low)",
> > and pass the low region by reusing DT property
> > "linux,usable-memory-range". We made the low memory region as the last
> > range of "linux,usable-memory-range" to keep compatibility with existing
> > user-space and older kdump kernels.
> >
> > Besides, we need to modify kexec-tools:
> > arm64: support more than one crash kernel regions(see [1])
> >
> > Another update is document about DT property 'linux,usable-memory-range':
> > schemas: update 'linux,usable-memory-range' node schema(see [2])
> >
> > This patchset contains the following 10 patches:
> >
> > 0001-0004 are some x86 cleanups which prepares for making functionsreserve_crashkernel[_low]() generic.
> > 0005 makes functions reserve_crashkernel[_low]() generic.
> > 0006-0007 reimplements arm64 crashkernel=X.
> > 0008-0009 adds memory for devices by DT property linux,usable-memory-range.
> > 0010 updates the doc.
> >
> > Changes since [v16]
> > - Because no functional changes in this version, so add
> > "Tested-by: Dave Kleikamp <dave.kleikamp@oracle.com>" for patch 1-9
> > - Add "Reviewed-by: Rob Herring <robh@kernel.org>" for patch 8
> > - Update patch 9 based on the review comments of Rob Herring
> > - As Catalin Marinas's suggestion, merge the implementation of
> > ARCH_WANT_RESERVE_CRASH_KERNEL into patch 5. Ensure that the
> > contents of X86 and ARM64 do not overlap, and reduce unnecessary
> > temporary differences.
>
> An Internal review has been done, so for this series,
>
> Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
That's good, but it would be _much_ better if you could do these reviews
on the public mailing list in future. Is that possible? Otherwise, it's
hard for maintainers to know what the reviews actually covered.
Thanks,
Will
_______________________________________________
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:[~2021-12-13 18:52 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 6:55 [PATCH v17 00/10] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2021-12-10 6:55 ` [PATCH v17 01/10] x86: kdump: replace the hard-coded alignment with macro CRASH_ALIGN Zhen Lei
2021-12-13 13:17 ` Baoquan He
2021-12-14 8:41 ` Leizhen (ThunderTown)
2021-12-13 14:26 ` john.p.donnelly
2021-12-13 19:54 ` Borislav Petkov
2021-12-14 9:27 ` Leizhen (ThunderTown)
2021-12-10 6:55 ` [PATCH v17 02/10] x86: kdump: make the lower bound of crash kernel reservation consistent Zhen Lei
2021-12-13 13:37 ` Baoquan He
2021-12-14 8:48 ` Leizhen (ThunderTown)
2021-12-13 14:27 ` john.p.donnelly
2021-12-14 19:07 ` Borislav Petkov
2021-12-14 19:24 ` Catalin Marinas
2021-12-15 2:10 ` Leizhen (ThunderTown)
2021-12-15 3:42 ` Baoquan He
2021-12-15 11:01 ` Catalin Marinas
2021-12-15 11:16 ` Baoquan He
2021-12-15 11:45 ` Leizhen (ThunderTown)
2021-12-10 6:55 ` [PATCH v17 03/10] x86: kdump: use macro CRASH_ADDR_LOW_MAX in functions reserve_crashkernel() Zhen Lei
2021-12-13 14:28 ` john.p.donnelly
2021-12-14 8:54 ` Baoquan He
2021-12-14 9:38 ` Borislav Petkov
2021-12-14 9:56 ` Baoquan He
2021-12-14 14:24 ` Borislav Petkov
2021-12-15 6:01 ` Baoquan He
2021-12-15 13:28 ` Borislav Petkov
2021-12-16 1:10 ` Baoquan He
2021-12-16 2:46 ` Leizhen (ThunderTown)
2021-12-16 11:07 ` Borislav Petkov
2021-12-16 12:08 ` Leizhen (ThunderTown)
2021-12-16 12:23 ` Leizhen (ThunderTown)
2021-12-16 14:48 ` Borislav Petkov
2021-12-17 2:51 ` Leizhen (ThunderTown)
2021-12-21 22:23 ` Borislav Petkov
2021-12-16 10:55 ` Borislav Petkov
2021-12-16 14:11 ` Baoquan He
2021-12-16 14:58 ` Borislav Petkov
2021-12-10 6:55 ` [PATCH v17 04/10] x86: kdump: move xen_pv_domain() check and insert_resource() to setup_arch() Zhen Lei
2021-12-13 14:29 ` john.p.donnelly
2021-12-14 11:40 ` Leizhen (ThunderTown)
2021-12-15 8:56 ` Leizhen (ThunderTown)
2021-12-15 9:22 ` Baoquan He
2021-12-10 6:55 ` [PATCH v17 05/10] x86: kdump: move reserve_crashkernel[_low]() into crash_core.c Zhen Lei
2021-12-13 14:30 ` john.p.donnelly
2021-12-14 10:45 ` Baoquan He
2021-12-14 12:38 ` Leizhen (ThunderTown)
2021-12-16 11:17 ` Borislav Petkov
2021-12-16 13:15 ` Leizhen (ThunderTown)
2021-12-16 14:51 ` Borislav Petkov
2021-12-10 6:55 ` [PATCH v17 06/10] arm64: kdump: introduce some macros for crash kernel reservation Zhen Lei
2021-12-13 14:30 ` john.p.donnelly
2021-12-10 6:55 ` [PATCH v17 07/10] arm64: kdump: reimplement crashkernel=X Zhen Lei
2021-12-13 14:31 ` john.p.donnelly
2021-12-10 6:55 ` [PATCH v17 08/10] of: fdt: Aggregate the processing of "linux, usable-memory-range" Zhen Lei
2021-12-10 16:39 ` [PATCH v17 08/10] of: fdt: Aggregate the processing of "linux,usable-memory-range" Rob Herring
2021-12-13 14:34 ` john.p.donnelly
2021-12-10 6:55 ` [PATCH v17 09/10] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2021-12-10 16:43 ` [PATCH v17 09/10] of: fdt: Add memory for devices by DT property "linux,usable-memory-range" Rob Herring
2021-12-13 14:33 ` john.p.donnelly
2021-12-10 6:55 ` [PATCH v17 10/10] kdump: update Documentation about crashkernel Zhen Lei
2021-12-13 14:34 ` john.p.donnelly
2021-12-10 7:15 ` [PATCH v17 00/10] support reserving crashkernel above 4G on arm64 kdump Kefeng Wang
2021-12-13 18:50 ` Will Deacon [this message]
2021-12-13 14:37 ` john.p.donnelly
2021-12-13 18:56 ` Catalin Marinas
2021-12-13 18:57 ` Borislav Petkov
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=20211213185054.GH12405@willie-the-truck \
--to=will@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dingguo.cz@antgroup.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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=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