From: Eric DeVolder <eric.devolder@oracle.com>
To: horms@verge.net.au, kexec@lists.infradead.org,
andrew.cooper3@citrix.com, dyoung@redhat.com, panand@redhat.com
Cc: daniel.kiper@oracle.com, konrad.wilk@oracle.com
Subject: [PATCH v4 0/11] kexec: Add option to get crash kernel region size
Date: Tue, 14 Feb 2017 15:09:12 -0600 [thread overview]
Message-ID: <1487106563-722-1-git-send-email-eric.devolder@oracle.com> (raw)
This is the fourth version of a patch series originally posted by
Daniel Kiper on December 5.
This version differs from the previous version based on feedback
received from the mailing list, as such:
v4: Incorporated feedback:
- additional changes for coding convention and formatting
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.
v2: Incorporated feedback:
- utilize the is_crashkernel_mem_reserved() function common in all archs
- for ppc and ppc64, utilize device-tree values to print size
- for unsupported architectures, print appropriate message
v1: Posted to kexec-tools mailing list
Eric
kexec/arch/arm/crashdump-arm.c | 5 +++++
kexec/arch/arm64/crashdump-arm64.c | 6 ++++++
kexec/arch/cris/kexec-cris.c | 6 ++++++
kexec/arch/ia64/crashdump-ia64.c | 5 +++++
kexec/arch/m68k/kexec-m68k.c | 6 ++++++
kexec/arch/mips/crashdump-mips.c | 4 ++++
kexec/arch/ppc/crashdump-powerpc.c | 27 ++++++++++++++++++++++++++-
kexec/arch/ppc/kexec-ppc.c | 28 ++++++++++++++++++++++++++++
kexec/arch/ppc/kexec-ppc.h | 1 +
kexec/arch/ppc64/crashdump-ppc64.c | 27 ++++++++++++++++++++++++++-
kexec/arch/ppc64/kexec-ppc64.c | 28 ++++++++++++++++++++++++++++
kexec/arch/ppc64/kexec-ppc64.h | 2 ++
kexec/arch/s390/kexec-s390.c | 5 +++++
kexec/arch/sh/crashdump-sh.c | 5 +++++
kexec/kexec.8 | 3 +++
kexec/kexec.c | 19 +++++++++++++++++++
kexec/kexec.h | 4 +++-
17 files changed, 178 insertions(+), 3 deletions(-)
Daniel Kiper (10):
crashdump/arm: Add get_crash_kernel_load_range() function
crashdump/cris: Add get_crash_kernel_load_range() function
crashdump/ia64: Add get_crash_kernel_load_range() function
crashdump/m68k: Add get_crash_kernel_load_range() function
crashdump/mips: Add get_crash_kernel_load_range() function
crashdump/ppc: Add get_crash_kernel_load_range() function
crashdump/ppc64: Add get_crash_kernel_load_range() function
crashdump/s390: Add get_crash_kernel_load_range() function
crashdump/sh: Add get_crash_kernel_load_range() function
kexec: Add option to get crash kernel region size
Eric DeVolder (1):
crashdump/arm64: Add get_crash_kernel_load_range() function
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2017-02-14 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:09 Eric DeVolder [this message]
2017-02-14 21:09 ` [PATCH v4 01/11] crashdump/arm: Add get_crash_kernel_load_range() function Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 02/11] crashdump/arm64: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 03/11] crashdump/cris: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 04/11] crashdump/ia64: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 05/11] crashdump/m68k: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 06/11] crashdump/mips: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 07/11] crashdump/ppc: " Eric DeVolder
2017-02-14 22:29 ` Daniel Kiper
2017-02-14 21:09 ` [PATCH v4 08/11] crashdump/ppc64: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 09/11] crashdump/s390: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 10/11] crashdump/sh: " Eric DeVolder
2017-02-14 21:09 ` [PATCH v4 11/11] kexec: Add option to get crash kernel region size Eric DeVolder
2017-02-14 22:34 ` 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=1487106563-722-1-git-send-email-eric.devolder@oracle.com \
--to=eric.devolder@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=dyoung@redhat.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=panand@redhat.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