From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
John Allen <jallen@linux.vnet.ibm.com>
Subject: Re: [REPOST PATCH v08 0/5] powerpc/hotplug: Update affinity for migrated CPUs
Date: Mon, 28 Jan 2019 09:45:37 -0600 [thread overview]
Message-ID: <eda0b416-ddf0-a533-120c-e73116065436@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180821153335.4955.44734.stgit@ltcalpine2-lp9.aus.stglabs.ibm.com>
On 8/21/18 10:33 AM, 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>
Retract this series in preference to
[PATCH] powerpc/pseries: Perform full re-add of CPU for topology update post-migration
Michael
>
> Michael Bringmann (5):
> hotplug/cpu: Conditionally acquire/release DRC index
> hotplug/cpu: Add operation queuing function
> hotplug/cpu: Provide CPU readd operation
> mobility/numa: Ensure numa update does not overlap
> hotplug/pmt: Update topology after PMT
> ---
> Changes in patch:
> -- Restructure and rearrange content of patches to co-locate
> similar or related modifications
> -- Rename pseries_update_drconf_cpu to pseries_update_processor
> -- Simplify code to update CPU nodes during mobility checks.
> Remove functions to generate extra HP_ELOG messages in favor
> of direct function calls to dlpar_cpu_readd_by_index.
> -- Revise code order in dlpar_cpu_readd_by_index() to present
> more appropriate error codes from underlying layers of the
> implementation.
> -- Add hotplug device lock around all property updates
> -- Add call to rebuild_sched_domains in case of changes
> -- Various code cleanups and compaction
> -- Rebase to 4.18 kernel
> -- Change operation to run CPU readd after end of migration store.
> -- Improve descriptive text
> -- Cleanup patch reference to outdated function
> -- Code cleanup a 'acquire_drc' check in dlpar_cpu_add.
> -- Code cleanup a 'release_drc' check in dlpar_cpu_remove.
> -- Add more information to patch descriptions.
> -- More code cleanup
> -- Rearrange call to rebuild_sched_domains to allow removal
> of some locking code.
>
--
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
parent reply other threads:[~2019-01-28 15:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180821153335.4955.44734.stgit@ltcalpine2-lp9.aus.stglabs.ibm.com>]
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=eda0b416-ddf0-a533-120c-e73116065436@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).