From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Michael Bringmann <mwb@linux.vnet.ibm.com>,
ltc-virtual-io@lists.linux.ibm.com
Subject: Re: [PATCH V6 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory
Date: Wed, 21 Jun 2017 19:54:32 +1000 [thread overview]
Message-ID: <8760fpu0mf.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <b0e02344-965b-5298-4ef6-3ec67d1200c4@linux.vnet.ibm.com>
Michael Bringmann <mwb@linux.vnet.ibm.com> writes:
> On Power systems with shared configurations of CPUs and memory, there
> are some issues with association of additional CPUs and memory to nodes
> when hot-adding resources. These patches address some of those problems.
>
> 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-specific code that defines the maximum number of nodes
> that the kernel will ever need in its current hardware environment.
> The boot code that initializes nodes for PowerPC will read this value
> and use it to ensure that all of the desired nodes are setup in the
> 'node_possible_map', and elsewhere.
>
> powerpc/numa: Correct the currently broken capability to set the
> topology for shared CPUs in LPARs. At boot time for shared CPU
> lpars, the topology for each shared CPU is set to node zero, however,
> this is now updated correctly using the Virtual Processor Home Node
> (VPHN) capabilities information provided by the pHyp. The VPHN handling
> in Linux is disabled, if PRRN handling is present.
>
> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
>
> Michael Bringmann (2):
> powerpc/hotplug: Add option to define max nodes allowing dynamic
> growth of resources.
> powerpc/numa: Update CPU topology when VPHN enabled
> ---
> Changes in V6:
> -- Reorder some code to better eliminate unused functions in
> conditional builds.
What changed between yesterday's V6 and this V6?
If you're going to resend, please bump the version number, we have tools
that parse the subject and version, and resending multiple times with
the same number breaks those.
cheers
next prev parent reply other threads:[~2017-06-21 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 15:14 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
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 ` Michael Ellerman [this message]
2017-06-21 14:18 ` [PATCH V6 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory Michael Bringmann
-- strict thread matches above, loose matches on Subject: below --
2017-06-19 22:09 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=8760fpu0mf.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ltc-virtual-io@lists.linux.ibm.com \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@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®