From: Eric DeVolder <eric.devolder@oracle.com>
To: kexec@lists.infradead.org, horms@verge.net.au, andrew.cooper3@citrix.com
Cc: daniel.kiper@oracle.com, konrad.wilk@oracle.com
Subject: [PATCH v5 01/11] crashdump/arm: Add get_crash_kernel_load_range() function
Date: Fri, 17 Feb 2017 16:47:15 -0600 [thread overview]
Message-ID: <1487371645-8299-2-git-send-email-eric.devolder@oracle.com> (raw)
In-Reply-To: <1487371645-8299-1-git-send-email-eric.devolder@oracle.com>
From: Daniel Kiper <daniel.kiper@oracle.com>
Implement get_crash_kernel_load_range() in support of
print crash kernel region size option.
Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
Signed-off-by: Eric DeVolder <eric.devolder@oracle.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
---
v5: Incorporated feedback:
- no changes for this arch
v4: Incorporated feedback:
- no changes for this arch
v3: Incorporated feedback:
- changes for coding convention and formatting
- restructured to introduce get_crash_kernel_load_range() for each
architecture, and then a single function in kexec/kexec.c to call
the per-architecture get_crash_kernel_load_range() and print the
result.
- print_crashkernel_region_size() changed to get_crash_kernel_load_range()
v2: Incorporated feedback:
- no changes for this arch
v1: Posted to kexec-tools mailing list
---
kexec/arch/arm/crashdump-arm.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/kexec/arch/arm/crashdump-arm.c b/kexec/arch/arm/crashdump-arm.c
index 4a89b5e..ac76e0a 100644
--- a/kexec/arch/arm/crashdump-arm.c
+++ b/kexec/arch/arm/crashdump-arm.c
@@ -413,3 +413,8 @@ int is_crashkernel_mem_reserved(void)
return crash_kernel_mem.start != crash_kernel_mem.end;
}
+
+int get_crash_kernel_load_range(uint64_t *start, uint64_t *end)
+{
+ return parse_iomem_single("Crash kernel\n", start, end);
+}
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-02-17 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:47 [PATCH v5 00/11] kexec: Add option to get crash kernel region size Eric DeVolder
2017-02-17 22:47 ` Eric DeVolder [this message]
2017-02-17 22:47 ` [PATCH v5 02/11] crashdump/arm64: Add get_crash_kernel_load_range() function Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 03/11] crashdump/cris: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 04/11] crashdump/ia64: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 05/11] crashdump/m68k: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 06/11] crashdump/mips: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 07/11] crashdump/ppc: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 08/11] crashdump/ppc64: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 09/11] crashdump/s390: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 10/11] crashdump/sh: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 11/11] kexec: Add option to get crash kernel region size Eric DeVolder
2017-03-02 9:51 ` [PATCH v5 00/11] " Simon Horman
2017-03-02 10:10 ` Daniel Kiper
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=1487371645-8299-2-git-send-email-eric.devolder@oracle.com \
--to=eric.devolder@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.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