linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	dyoung@redhat.com, ebiederm@xmission.com, vgoyal@redhat.com,
	linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
	kexec@lists.infradead.org, lkml <linux-kernel@vger.kernel.org>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: [PATCH v3 0/2] powerpc/fadump: support memory range syntax for fadump memory reservation
Date: Wed, 10 Aug 2016 15:34:51 +0530	[thread overview]
Message-ID: <147082324660.4631.6557186560310369015.stgit@hbathini.in.ibm.com> (raw)

This patchset adds support to input system memory range based memory size
for fadump reservation. The crashkernel parameter already supports such
syntax. The first patch refactors the parsing code of crashkernel parameter
for reuse. The second patch uses the newly refactored parsing code to reserve
memory for fadump based on system memory size.

---

Hari Bathini (2):
      kexec: refactor code parsing size based on memory range
      powerpc/fadump: parse fadump reserve memory size based on memory range


 arch/powerpc/kernel/fadump.c |   63 ++++++++++++++++++++++---
 include/linux/kernel.h       |    5 ++
 kernel/kexec_core.c          |   63 ++-----------------------
 lib/cmdline.c                |  104 ++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 168 insertions(+), 67 deletions(-)

             reply	other threads:[~2016-08-10 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 10:04 Hari Bathini [this message]
2016-08-10 10:05 ` [PATCH v3 1/2] kexec: refactor code parsing size based on memory range Hari Bathini
2016-08-10 10:05 ` [PATCH v3 2/2] powerpc/fadump: parse fadump reserve memory " Hari Bathini
2016-08-25  7:01   ` Dave Young
2016-08-25 17:30     ` Hari Bathini
2016-08-26  3:22       ` Dave Young

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=147082324660.4631.6557186560310369015.stgit@hbathini.in.ibm.com \
    --to=hbathini@linux.vnet.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=vgoyal@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;
as well as URLs for NNTP newsgroup(s).