From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: nfont@linux.vnet.ibm.com,
Michael Bringmann from Kernel Team <mbringm@us.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: [PATCH V10 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory
Date: Thu, 24 Aug 2017 17:07:21 -0500 [thread overview]
Message-ID: <db1b23c1-67bc-fb0f-51f9-af4bc564d9ef@linux.vnet.ibm.com> (raw)
From: mwb@linux.vnet.ibm.com
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: nfont@linux.vnet.ibm.com
Cc: mwb@linux.vnet.ibm.com
Subject: [PATCH V10 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory
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/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.
Also, update initialization checks for device-tree attributes to
independently recognize PRRN or VPHN usage.
Finally, try to distinguish the VPHN code from the NUMA code better,
and move relevant functions to another file.
powerpc/nodes: 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.
This patch extracts the value of the 'min_common_depth' element from
the "rtas" device tree property "ibm,max-associativity-domains" to use
as the maximum number of nodes to setup as possibly available in the
system. [The 'min_common_depth' element is calculated from memory
associations found while loading all of the configured memory into
the system data structures at boot.] This new setting will override
the instruction,
nodes_and(node_possible_map, node_possible_map, node_online_map);
presently seen in the function arch/powerpc/mm/numa.c:initmem_init().
If the property is not present at boot, no operation will be performed
to define or enable additional nodes.
Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Michael Bringmann (2):
powerpc/numa: Update CPU topology when VPHN enabled
powerpc/nodes: Ensure enough nodes avail for operations
---
Changes in V10:
-- Reorganize VPHN code
-- Revise index used with property "ibm,max-associativity-domains"
next reply other threads:[~2017-08-24 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 22:07 Michael Bringmann [this message]
2017-08-24 22:07 ` [PATCH V10 1/2] powerpc/numa: Update CPU topology when VPHN enabled Michael Bringmann
2017-08-28 16:25 ` Nathan Fontenot
2017-08-24 22:07 ` [PATCH V10 2/2] powerpc/nodes: 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=db1b23c1-67bc-fb0f-51f9-af4bc564d9ef@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mbringm@us.ibm.com \
--cc=mpe@ellerman.id.au \
--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®