All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [3/3] powerpc/fadump: add support for fadump_nr_cpus= parameter
Date: Mon, 9 May 2016 15:05:58 +0530	[thread overview]
Message-ID: <573059FE.7080706@linux.vnet.ibm.com> (raw)
In-Reply-To: <3r1wGk6H7Yz9t3k@ozlabs.org>



On 05/07/2016 09:42 AM, Michael Ellerman wrote:
> On Fri, 2016-06-05 at 11:51:08 UTC, Hari Bathini wrote:
>> Kernel parameter 'nr_cpus' can be used to limit the maximum number
>> of processors that an SMP kernel could support. This patch extends
>> this to fadump by introducing 'fadump_nr_cpus' parameter that can
>> help in booting fadump kernel on a lower memory footprint.
> Is there really no other way to do this? I really hate adding new, single use
> only command line parameters.

Hmmm.. only alternative I can think about is enforcing a certain nr_cpu_ids
value whenever fadump is active, but that doesn't sound right..
Any suggestions?

Thanks
Hari

> cheers
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

      reply	other threads:[~2016-05-09  9:37 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
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 [this message]

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=573059FE.7080706@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.