From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [PATCH v21 3/5] arm64: kdump: reimplement crashkernel=X
Date: Thu, 17 Mar 2022 10:38:38 +0800 [thread overview]
Message-ID: <YjKfLo4YgSBG8v61@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220227030717.1464-4-thunder.leizhen@huawei.com>
On 02/27/22 at 11:07am, Zhen Lei wrote:
> From: Chen Zhou <chenzhou10@huawei.com>
>
> 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
~~ change it to "get boot failure" or "fail to boot"
> for allocation.
>
> To solve these issues, change the behavior of crashkernel=X and
> introduce crashkernel=X,[high,low]. 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 region above DMA zone,
> which also tries to allocate at least 256M in DMA zone automatically.
> "crashkernel=Y,low" can be used to allocate specified size low memory.
>
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> Co-developed-by: Zhen Lei <thunder.leizhen@huawei.com>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
next prev parent reply other threads:[~2022-03-17 2:38 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
2022-03-16 5:17 ` Baoquan He
2022-03-16 5:39 ` Baoquan He
2022-03-16 6:15 ` Leizhen
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
2022-03-17 2:36 ` Baoquan He
2022-03-17 3:19 ` Leizhen
2022-03-17 3:47 ` Baoquan He
2022-03-17 7:30 ` Leizhen
2022-03-17 2:38 ` Baoquan He [this message]
2022-03-17 3:23 ` Leizhen
2022-03-21 13:29 ` John Donnelly
2022-03-21 14:09 ` Dave Kleikamp
2022-03-22 1:58 ` Leizhen
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
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
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=YjKfLo4YgSBG8v61@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.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