From: Arnd Bergmann <arnd@arndb.de>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: Simon Horman <horms@verge.net.au>,
john.p.donnelly@oracle.com, Will Deacon <will@kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Bhupesh Sharma <bhsharma@redhat.com>,
kexec@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, James Morse <james.morse@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
pkushwaha@marvell.com, Dave Young <dyoung@redhat.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 0/4] support reserving crashkernel above 4G on arm64 kdump
Date: Tue, 19 May 2020 12:21:55 +0200 [thread overview]
Message-ID: <CAK8P3a2VrAqefPYF2JqRjwdhgTDtORUgWgVuYxRYWqKxE3+5pA@mail.gmail.com> (raw)
In-Reply-To: <a57d46bc-881e-3526-91ca-558bf64e2aa8@huawei.com>
On Thu, Mar 26, 2020 at 4:10 AM Chen Zhou <chenzhou10@huawei.com> wrote:
>
> Hi all,
>
> Friendly ping...
I was asked about this patch series, and see that you last posted it in
December. I think you should rebase it to linux-5.7-rc6 and post the
entire series again to make progress, as it's unlikely that any maintainer
would pick up the patches from last year.
For the contents, everything seems reasonable to me, but I noticed that
you are adding a property to the /chosen node without adding the
corresponding documentation to
Documentation/devicetree/bindings/chosen.txt
Please add that, and Cc the devicetree maintainers on the updated
patch.
Arnd
> On 2019/12/23 23:23, Chen Zhou wrote:
> > This patch series enable reserving crashkernel above 4G in arm64.
> >
> > 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. Currently, crashkernel=Y@X can be used to reserve crashkernel above 4G,
> > in this case, if swiotlb or DMA buffers are required, crash dump kernel
> > will boot failure because there is no low memory available for allocation.
> >
> > The previous changes and discussions can be retrieved from:
> >
> > Changes since [v6]
> > - Fix build errors reported by kbuild test robot.
...
_______________________________________________
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:[~2020-05-19 10:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 15:23 [PATCH v7 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-12-23 15:23 ` [PATCH v7 1/4] x86: kdump: move reserve_crashkernel_low() into crash_core.c Chen Zhou
2019-12-27 5:54 ` Dave Young
2019-12-27 11:04 ` Chen Zhou
2019-12-28 9:32 ` Dave Young
2019-12-31 1:39 ` Chen Zhou
2020-04-03 7:13 ` Chen Zhou
2020-01-16 15:17 ` James Morse
2020-01-16 15:47 ` John Donnelly
2020-02-24 15:25 ` John Donnelly
2020-03-02 1:29 ` Chen Zhou
2020-01-17 3:58 ` Dave Young
2020-04-03 7:29 ` Chen Zhou
2019-12-23 15:23 ` [PATCH v7 2/4] arm64: kdump: reserve crashkenel above 4G for crash dump kernel Chen Zhou
2020-03-05 10:13 ` Prabhakar Kushwaha
2020-03-07 11:06 ` Chen Zhou
2020-03-07 18:43 ` John Donnelly
2020-03-09 4:59 ` Prabhakar Kushwaha
2020-03-09 4:48 ` Prabhakar Kushwaha
2020-03-09 15:51 ` Prabhakar Kushwaha
2020-03-10 1:30 ` chenzhou
2020-03-10 17:08 ` Prabhakar Kushwaha
2020-03-11 1:44 ` chenzhou
2019-12-23 15:23 ` [PATCH v7 3/4] arm64: kdump: add memory for devices by DT property, low-memory-range Chen Zhou
2019-12-23 15:23 ` [PATCH v7 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2020-03-26 3:09 ` [PATCH v7 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2020-05-19 10:21 ` Arnd Bergmann [this message]
2020-05-19 20:21 ` John Donnelly
2020-05-20 8:32 ` Bhupesh Sharma
2020-05-20 3:30 ` chenzhou
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=CAK8P3a2VrAqefPYF2JqRjwdhgTDtORUgWgVuYxRYWqKxE3+5pA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=bhsharma@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=chenzhou10@huawei.com \
--cc=dyoung@redhat.com \
--cc=horms@verge.net.au \
--cc=james.morse@arm.com \
--cc=john.p.donnelly@oracle.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=pkushwaha@marvell.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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).