From: Rob Herring <robh@kernel.org>
To: kexec@lists.infradead.org
Subject: [PATCH v23 5/6] of: Support more than one crash kernel regions for kexec -s
Date: Thu, 5 May 2022 15:03:03 -0500 [thread overview]
Message-ID: <YnQtd5+iSXj+R5X/@robh.at.kernel.org> (raw)
In-Reply-To: <20220505091845.167-6-thunder.leizhen@huawei.com>
On Thu, 05 May 2022 17:18:44 +0800, Zhen Lei wrote:
> When "crashkernel=X,high" is used, there may be two crash regions:
> high=crashk_res and low=crashk_low_res. But now the syscall
> kexec_file_load() only add crashk_res into "linux,usable-memory-range",
> this may cause the second kernel to have no available dma memory.
>
> Fix it like kexec tool do for option -c, add both 'high' and 'low' regions
> into the dtb.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> drivers/of/kexec.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-05 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 9:18 [PATCH v23 0/6] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2022-05-05 9:18 ` [PATCH v23 1/6] kdump: return -ENOENT if required cmdline option does not exist Zhen Lei
2022-05-05 9:18 ` [PATCH v23 2/6] arm64: Use insert_resource() to simplify code Zhen Lei
2022-05-05 9:18 ` [PATCH v23 3/6] arm64: kdump: Reimplement crashkernel=X Zhen Lei
2022-05-05 17:01 ` Catalin Marinas
2022-05-06 3:22 ` Leizhen
2022-05-06 11:06 ` Catalin Marinas
2022-05-06 12:35 ` Leizhen
2022-05-06 13:16 ` Baoquan He
2022-05-06 17:45 ` Catalin Marinas
2022-05-07 10:45 ` Baoquan He
2022-05-05 9:18 ` [PATCH v23 4/6] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2022-05-05 9:18 ` [PATCH v23 5/6] of: Support more than one crash kernel regions for kexec -s Zhen Lei
2022-05-05 20:03 ` Rob Herring [this message]
2022-05-05 9:18 ` [PATCH v23 6/6] docs: kdump: Update the crashkernel description for arm64 Zhen Lei
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=YnQtd5+iSXj+R5X/@robh.at.kernel.org \
--to=robh@kernel.org \
--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