linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Michael Bringmann <mwb@linux.vnet.ibm.com>,
	Nathan Fontenot <nfont@linux.vnet.ibm.com>,
	John Allen <jallen@linux.vnet.ibm.com>,
	Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
	Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Subject: [PATCH v04 0/9] powerpc/hotplug: Update affinity for migrated CPUs
Date: Wed, 20 Jun 2018 19:28:09 -0500	[thread overview]
Message-ID: <0425b353-54b0-6ccd-fbb6-3d26d9448bb5@linux.vnet.ibm.com> (raw)

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>

Michael Bringmann (9):
  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
  numa: Disable/enable arch_update_cpu_topology
  pmt/numa: Disable arch_update_cpu_topology during CPU readd
  powerpc/rtas: Allow disabling rtas_event_scan
  hotplug/rtas: No rtas_event_scan during property update
  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.17-rc5 kernel

             reply	other threads:[~2018-06-21  0:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21  0:28 Michael Bringmann [this message]
2018-06-21  0:29 ` [PATCH v04 1/9] hotplug/cpu: Conditionally acquire/release DRC index Michael Bringmann
2018-06-21  0:29 ` [PATCH v04 2/9] hotplug/cpu: Add operation queuing function Michael Bringmann
2018-06-21  0:29 ` [PATCH v04 3/9] hotplug/cpu: Provide CPU readd operation Michael Bringmann
2018-06-21  0:29 ` [PATCH v04 4/9] mobility/numa: Ensure numa update does not overlap Michael Bringmann
2018-06-21  0:29 ` [PATCH v04 5/9] numa: Disable/enable arch_update_cpu_topology Michael Bringmann
2018-06-21  0:30 ` [PATCH v04 6/9] pmt/numa: Disable arch_update_cpu_topology during CPU readd Michael Bringmann
2018-06-21  0:30 ` [PATCH v04 7/9] powerpc/rtas: Allow disabling rtas_event_scan Michael Bringmann
2018-06-21  0:30 ` [PATCH v04 8/9] hotplug/rtas: No rtas_event_scan during PMT update Michael Bringmann
2018-06-21  0:30 ` [PATCH v04 9/9] hotplug/pmt: Update topology after PMT Michael Bringmann
2018-06-21  0:49   ` Michael Bringmann
2018-06-21  2:13   ` kbuild test robot
2018-06-21 19:37     ` Michael Bringmann
2018-06-21 19:37     ` 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=0425b353-54b0-6ccd-fbb6-3d26d9448bb5@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).