From: Levi Yun <ppbuk5246@gmail.com>
To: bhe@redhat.com, will@kernel.org, nramas@linux.microsoft.com,
thunder.leizhen@huawei.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
Levi Yun <ppbuk5246@gmail.com>
Subject: [PATCH v2] arm64/kexec: Fix missing extra range for crashkres_low.
Date: Tue, 30 Aug 2022 18:28:39 +0900 [thread overview]
Message-ID: <20220830092839.3197-1-ppbuk5246@gmail.com> (raw)
In-Reply-To: <CAM7-yPTdihLsPjDKM-0OEszxNd8n0bgeRseiEkCsSZW-uuaRvw@mail.gmail.com>
Like crashk_res, Calling crash_exclude_mem_range function with
crashk_low_res area would need extra crash_mem range too.
Add one more extra cmem range slot in case of crashk_low_res is used.
Signed-off-by: Levi Yun <ppbuk5246@gmail.com>
---
arch/arm64/kernel/machine_kexec_file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/machine_kexec_file.c b/arch/arm64/kernel/machine_kexec_file.c
index 889951291cc0..a11a6e14ba89 100644
--- a/arch/arm64/kernel/machine_kexec_file.c
+++ b/arch/arm64/kernel/machine_kexec_file.c
@@ -47,7 +47,7 @@ static int prepare_elf_headers(void **addr, unsigned long *sz)
u64 i;
phys_addr_t start, end;
- nr_ranges = 1; /* for exclusion of crashkernel region */
+ nr_ranges = 2; /* for exclusion of crashkernel region */
for_each_mem_range(i, &start, &end)
nr_ranges++;
--
2.35.1
next prev parent reply other threads:[~2022-08-30 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 15:12 [PATCH] arm64/kexec: Fix missing extra range for crashkres_low Levi Yun
2022-08-30 4:28 ` [PATCH-RESEND] " Yun Levi
2022-08-30 7:37 ` Baoquan He
2022-08-30 8:30 ` Yun Levi
2022-08-30 9:28 ` Levi Yun [this message]
2022-08-30 12:46 ` [PATCH v2] " Baoquan He
2022-08-30 16:40 ` Catalin Marinas
2022-08-31 0:38 ` Yun Levi
2022-08-31 1:18 ` Baoquan He
2022-08-31 1:31 ` Yun Levi
2022-08-31 1:49 ` [PATCH v2-RESEND] " Yun Levi
2022-08-31 10:26 ` Catalin Marinas
2022-08-31 10:29 ` Yun Levi
2022-08-31 10:39 ` [PATCH v3] " Levi Yun
2022-09-01 13:06 ` Will Deacon
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=20220830092839.3197-1-ppbuk5246@gmail.com \
--to=ppbuk5246@gmail.com \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=thunder.leizhen@huawei.com \
--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).