mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	Reza Arbab <arbab@linux.vnet.ibm.com>,
	John Allen <jallen@linux.vnet.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	Shailendra Singh <shailendras@nvidia.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Rashmica Gupta <rashmicy@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
	Michael Bringmann from Kernel Team <mbringm@us.ibm.com>,
	Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: [PATCH V6 1/2] powerpc/hotplug: Ensure enough nodes avail for operations
Date: Wed, 21 Jun 2017 09:24:59 -0500	[thread overview]
Message-ID: <75a86b88-ae0c-93c1-dade-85d5e8315610@linux.vnet.ibm.com> (raw)
In-Reply-To: <878tklu0pw.fsf@concordia.ellerman.id.au>



On 06/21/2017 04:52 AM, Michael Ellerman wrote:
> Michael Bringmann <mwb@linux.vnet.ibm.com> writes:
> 
>> powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU
>> or memory resources, it may occur that the new resources are to be
>> inserted into nodes that were not used for these resources at bootup.
>> In the kernel, any node that is used must be defined and initialized
>> at boot.  In order to meet both needs, this patch adds a new kernel
>> command line option (numnodes=<int>) for use by the PowerPC architecture-
> 
> Sorry, that's a hack.

It is an intermediate step pending the provision of the firmware properties
under discussion that were mentioned by Nathan Fontenot last week.

> I thought you were going to use firmware properties to find the set of
> possible nodes. Did that not work?

Inference based on the current set of firmware properties for associativity
is insufficient.  That is partly the reason for the properties mentioned by
Nathan last week.  The current firmware properties only cover what is known
at boot time.  They do not cover expansions from DLPAR / hot-add operations
which can add up to everything else on the system.

> cheers

Regards,

-- 
Michael W. Bringmann
Linux Technology Center
IBM Corporation
Tie-Line  363-5196
External: (512) 286-5196
Cell:       (512) 466-0650
mwb@linux.vnet.ibm.com

  reply	other threads:[~2017-06-21 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 15:14 [PATCH V6 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory Michael Bringmann
2017-06-20 15:14 ` [PATCH V6 1/2] powerpc/hotplug: Ensure enough nodes avail for operations Michael Bringmann
2017-06-21  9:52   ` Michael Ellerman
2017-06-21 14:24     ` Michael Bringmann [this message]
2017-06-20 15:15 ` [PATCH V6 2/2] powerpc/numa: Update CPU topology when VPHN enabled Michael Bringmann
2017-06-25  0:04   ` kbuild test robot
2017-06-21  9:54 ` [PATCH V6 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory Michael Ellerman
2017-06-21 14:18   ` Michael Bringmann
  -- strict thread matches above, loose matches on Subject: below --
2017-06-19 22:09 Michael Bringmann
2017-06-19 22:10 ` [PATCH V6 1/2] powerpc/hotplug: Ensure enough nodes avail for operations Michael Bringmann

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=75a86b88-ae0c-93c1-dade-85d5e8315610@linux.vnet.ibm.com \
    --to=mwb@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=arbab@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=bigeasy@linutronix.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=jallen@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mbringm@us.ibm.com \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=rashmicy@gmail.com \
    --cc=shailendras@nvidia.com \
    --cc=tglx@linutronix.de \
    --cc=tyreld@linux.vnet.ibm.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

all inboxes | Powered by JetHome®