From: Michael Ellerman <patch-notifications@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>,
John Allen <jallen@linux.vnet.ibm.com>
Subject: Re: [V14,1/4] powerpc/vphn: Update CPU topology when VPHN enabled
Date: Thu, 19 Oct 2017 15:48:23 +1100 (AEDT) [thread overview]
Message-ID: <3yHbzC4qg0z9tXC@ozlabs.org> (raw)
In-Reply-To: <e7dde327-f78a-31a4-ce0f-8fbf67459f64@linux.vnet.ibm.com>
On Fri, 2017-09-08 at 20:47:27 UTC, Michael Bringmann wrote:
> powerpc/vphn: On Power systems with shared configurations of CPUs
> and memory, there are some issues with the association of additional
> CPUs and memory to nodes when hot-adding resources. This patch
> corrects the currently broken capability to set the topology for
> shared CPUs in LPARs. At boot time for shared CPU lpars, the
> topology for each CPU was being set to node zero. Now when
> numa_update_cpu_topology() is called appropriately, the Virtual
> Processor Home Node (VPHN) capabilities information provided by the
> pHyp allows the appropriate node in the shared configuration to be
> selected for the CPU.
>
> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/17f444c0549f2ce037646871e748cf
cheers
next prev parent reply other threads:[~2017-10-19 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 20:47 [PATCH V14 0/4] " Michael Bringmann
2017-09-08 20:47 ` [PATCH V14 1/4] " Michael Bringmann
2017-10-19 4:48 ` Michael Ellerman [this message]
2017-09-08 20:47 ` [PATCH V14 2/4] powerpc/vphn: Improve recognition of PRRN/VPHN Michael Bringmann
2017-09-08 20:47 ` [PATCH V14 3/4] powerpc/hotplug: Improve responsiveness of hotplug change Michael Bringmann
2017-09-08 20:47 ` [PATCH V14 4/4] powerpc/vphn: Fix numa update end-loop bug 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=3yHbzC4qg0z9tXC@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=jallen@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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®