All of lore.kernel.org
 help / color / mirror / Atom feed
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 06/11] crashdump/mips: Add get_crash_kernel_load_range() function
Date: Tue, 14 Feb 2017 15:09:18 -0600	[thread overview]
Message-ID: <1487106563-722-7-git-send-email-eric.devolder@oracle.com> (raw)
In-Reply-To: <1487106563-722-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>
---
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/mips/crashdump-mips.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/kexec/arch/mips/crashdump-mips.c b/kexec/arch/mips/crashdump-mips.c
index d6cff5a..9c33599 100644
--- a/kexec/arch/mips/crashdump-mips.c
+++ b/kexec/arch/mips/crashdump-mips.c
@@ -385,3 +385,7 @@ int is_crashkernel_mem_reserved(void)
 		(start != end) : 0;
 }
 
+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

  parent 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 [PATCH v4 0/11] kexec: Add option to get crash kernel region size Eric DeVolder
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 ` Eric DeVolder [this message]
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-7-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.