linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org,
	Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
	Thomas Falcon <tlfalcon@linux.vnet.ibm.com>,
	John Allen <jallen@linux.vnet.ibm.com>
Subject: Re: [PATCH v08 0/5] powerpc/hotplug: Update affinity for migrated CPUs
Date: Mon, 5 Nov 2018 11:50:17 -0600	[thread overview]
Message-ID: <a0fb8d89-c0a9-b8fe-e099-c186ab2e3b63@linux.vnet.ibm.com> (raw)
In-Reply-To: <20181029205127.3987eaaa@kitsune.suse.cz>

On 10/29/2018 02:51 PM, Michal Suchánek wrote:
> On Sun, 29 Jul 2018 08:18:34 -0500
> Michael Bringmann <mwb@linux.vnet.ibm.com> wrote:
> 
>> The migration of LPARs across Power systems affects many attributes
>> including that of the associativity of CPUs.  The patches in this
>> set execute when a system is coming up fresh upon a migration target.
>> They are intended to,
>>
>> * Recognize changes to the associativity of CPUs recorded in internal
>>   data structures when compared to the latest copies in the device
>> tree.
>> * Generate calls to other code layers to reset the data structures
>>   related to associativity of the CPUs.
>> * Re-register the 'changed' entities into the target system.
>>   Re-registration of CPUs mostly entails acting as if they have been
>>   newly hot-added into the target system.
>>
>> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
>>
> Hello,
> 
> what is the status of this patchset other than it no longer applies?

The current PowerPC systems already perform remove_processor /
add_processor operations during migration events that subsume
the necessary affinity changes.  This patchset was overkill,
so we pulled it.

Memory affinity on the other hand does need intervention, and that
patchset has been posted.  I was just about to ping Michael Ellerman
about the status from his end.
 
> 
> Thanks
> 
> Michal

Thanks.
Michael

-- 
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:[~2018-11-05 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 13:18 [PATCH v08 0/5] powerpc/hotplug: Update affinity for migrated CPUs Michael Bringmann
2018-07-29 13:19 ` [PATCH v08 1/5] hotplug/cpu: Conditionally acquire/release DRC index Michael Bringmann
2018-07-29 13:19 ` [PATCH v08 4/5] mobility/numa: Ensure numa update does not overlap Michael Bringmann
2018-07-29 13:19 ` [PATCH v08 5/5] hotplug/pmt: Update topology after PMT Michael Bringmann
2018-10-29 19:51 ` [PATCH v08 0/5] powerpc/hotplug: Update affinity for migrated CPUs Michal Suchánek
2018-11-05 17:50   ` Michael Bringmann [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=a0fb8d89-c0a9-b8fe-e099-c186ab2e3b63@linux.vnet.ibm.com \
    --to=mwb@linux.vnet.ibm.com \
    --cc=jallen@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=tlfalcon@linux.vnet.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).