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: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Reza Arbab <arbab@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Bharata B Rao <bharata@linux.vnet.ib>,
Balbir Singh <bsingharora@gmail.com>,
Michael Bringmann <mwb@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>
Subject: Re: [PATCH V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc
Date: Fri, 26 May 2017 15:38:15 +1000 [thread overview]
Message-ID: <87tw4889fc.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <9b006866-5a8e-dc05-d603-bfe8eb02eef2@linux.vnet.ibm.com>
Michael Bringmann <mwb@linux.vnet.ibm.com> writes:
> Removing or adding memory via the PowerPC hotplug interface shows
> anomalies in the association between memory and nodes.
What anomalies? Please describe the actual problem you're seeing, with
details, and why you think this is the correct fix.
This is a revert of 3af229f2071f ("powerpc/numa: Reset node_possible_map
to only node_online_map"), so please explain why all the things
mentioned in the change log for that commit are either wrong or no
longer true.
cheers
prev parent reply other threads:[~2017-05-26 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170525171932.29159.89311.stgit@ltcalpine2-lp20.aus.stglabs.ibm.com>
2017-05-25 17:35 ` [PATCH V2 1/2] powerpc/numa: Update CPU topology when VPHN enabled Michael Bringmann
2017-05-25 22:05 ` Tyrel Datwyler
2017-05-26 17:19 ` kbuild test robot
2017-05-25 17:37 ` [PATCH V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc Michael Bringmann
2017-05-26 3:23 ` Balbir Singh
2017-05-26 12:28 ` Michael Bringmann
2017-05-26 5:38 ` Michael Ellerman [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=87tw4889fc.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arbab@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bharata@linux.vnet.ib \
--cc=bigeasy@linutronix.de \
--cc=bsingharora@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=shailendras@nvidia.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome