From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [2/3] powerpc/fadump: add support to specify memory range based size
Date: Mon, 9 May 2016 15:07:39 +0530 [thread overview]
Message-ID: <57305A63.80702@linux.vnet.ibm.com> (raw)
In-Reply-To: <3r1wDn0JV0z9t3k@ozlabs.org>
On 05/07/2016 09:41 AM, Michael Ellerman wrote:
> On Fri, 2016-06-05 at 11:50:37 UTC, Hari Bathini wrote:
>> Currently, memory for fadump can be specified with fadump_reserve_mem=size,
>> where only a fixed size can be specified. This patch tries to extend this
>> syntax to support conditional reservation based on memory size, with the
>> below syntax:
>>
>> fadump_reserve_mem=<range1>:<size1>[,<range2>:<size2>,...]
>>
>> This syntax helps using the same commandline parameter for different system
>> memory sizes.
> This is basically using the crashkernel= syntax right?
Yep. One of the typical crashkernel syntax..
> So can we please reuse the crashkernel= parsing code?
but crashkernel has a few other variants which don't make sense
for fadump. To reuse the crashkernel parsing code for fadump,
it needs little bit of refactoring. Will try to do that and respin..
> cheers
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2016-05-09 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 11:50 [PATCH 1/3] powerpc/fadump: set an upper limit for the default memory reserved for fadump Hari Bathini
2016-05-06 11:50 ` [PATCH 2/3] powerpc/fadump: add support to specify memory range based size Hari Bathini
2016-05-07 4:11 ` [2/3] " Michael Ellerman
2016-05-09 9:37 ` Hari Bathini [this message]
2016-05-06 11:51 ` [PATCH 3/3] powerpc/fadump: add support for fadump_nr_cpus= parameter Hari Bathini
2016-05-07 4:12 ` [3/3] " Michael Ellerman
2016-05-09 9:35 ` Hari Bathini
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=57305A63.80702@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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.