From: Chen Zhou <chenzhou10@huawei.com>
To: catalin.marinas@arm.com, will.deacon@arm.com,
akpm@linux-foundation.org, rppt@linux.ibm.com,
ard.biesheuvel@linaro.org, takahiro.akashi@linaro.org
Cc: wangkefeng.wang@huawei.com, Chen Zhou <chenzhou10@huawei.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] support reserving crashkernel above 4G on arm64 kdump
Date: Wed, 3 Apr 2019 11:05:43 +0800 [thread overview]
Message-ID: <20190403030546.23718-1-chenzhou10@huawei.com> (raw)
When crashkernel is reserved above 4G in memory, kernel should reserve
some amount of low memory for swiotlb and some DMA buffers. So there may
be two crash kernel regions, one is below 4G, the other is above 4G.
Crash dump kernel reads more than one crash kernel regions via a dtb
property under node /chosen,
linux,usable-memory-range = <BASE1 SIZE1 [BASE2 SIZE2]>.
Besides, we need to modify kexec-tools:
arm64: support more than one crash kernel regions
Chen Zhou (3):
arm64: kdump: support reserving crashkernel above 4G
arm64: kdump: support more than one crash kernel regions
kdump: update Documentation about crashkernel on arm64
Documentation/admin-guide/kernel-parameters.txt | 4 +-
arch/arm64/kernel/setup.c | 3 +
arch/arm64/mm/init.c | 108 ++++++++++++++++++++----
include/linux/memblock.h | 1 +
mm/memblock.c | 40 +++++++++
5 files changed, 139 insertions(+), 17 deletions(-)
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2019-04-03 3:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 3:05 Chen Zhou [this message]
2019-04-03 3:05 ` [PATCH 1/3] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-04-04 14:46 ` Mike Rapoport
2019-04-05 3:03 ` Chen Zhou
2019-04-03 3:05 ` [PATCH 2/3] arm64: kdump: support more than one crash kernel regions Chen Zhou
2019-04-03 11:29 ` Mike Rapoport
2019-04-03 13:51 ` Chen Zhou
2019-04-04 14:44 ` Mike Rapoport
2019-04-05 2:17 ` Chen Zhou
2019-04-05 3:47 ` Chen Zhou
2019-04-08 6:57 ` Mike Rapoport
2019-04-08 8:39 ` Chen Zhou
2019-04-08 15:38 ` Chen Zhou
2019-04-03 3:05 ` [PATCH 3/3] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-04-09 5:20 ` [PATCH 0/3] support reserving crashkernel above 4G on arm64 kdump Bhupesh Sharma
2019-04-09 9:07 ` Chen Zhou
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=20190403030546.23718-1-chenzhou10@huawei.com \
--to=chenzhou10@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--cc=takahiro.akashi@linaro.org \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.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