From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Michael Ellerman <mpe@ellerman.id.au>,
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: Re: [PATCH V2 0/3] powerpc/hotplug: Fix affinity assoc for LPAR migration
Date: Tue, 28 Nov 2017 16:30:49 -0600 [thread overview]
Message-ID: <e9689260-c088-9fd7-3883-0bd8cfed744d@linux.vnet.ibm.com> (raw)
In-Reply-To: <030d7727-9b39-f9ab-53e6-6a47605ac6b3@linux.vnet.ibm.com>
Hello:
I would like to pull / defer further consideration of this patch set
for a while. I will be discussing changes here with respect to the
LMB optimizations that Nathan Fontenot is working upon.
A revision of this patch set will be sent out somewhat later.
Thanks for your attention and assistance.
Michael
On 11/16/2017 11:50 AM, Michael Bringmann wrote:
> The migration of LPARs across Power systems affects many attributes
> including that of the associativity of memory blocks and 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 memory and CPUs recorded
> in internal data structures when compared to the latest copies in
> the device tree (e.g. ibm,dynamic-memory, ibm,dynamic-memory-v2,
> cpus),
> * Recognize changes to the associativity mapping (e.g. ibm,
> associativity-lookup-arrays), locate all assigned memory blocks
> corresponding to each changed row, and readd all such blocks.
> * Generate calls to other code layers to reset the data structures
> related to associativity of the CPUs and memory.
> * Re-register the 'changed' entities into the target system.
> Re-registration of CPUs and memory blocks 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 (3):
> hotplug/mobility: Apply assoc lookup updates for Post Migration Topo
> postmigration/memory: Review assoc lookup array changes
> postmigration/memory: Associativity & 'ibm,dynamic-memory-v2'
> ---
> Changes in V2:
> -- Try to improve patch header documentation.
> -- Remove unnecessary spacing changes from patch
>
--
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
prev parent reply other threads:[~2017-11-28 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 17:50 [PATCH V2 0/3] powerpc/hotplug: Fix affinity assoc for LPAR migration Michael Bringmann
2017-11-16 17:50 ` [PATCH V2 1/3] hotplug/mobility: Apply assoc updates for Post Migration Topo Michael Bringmann
2017-11-20 16:04 ` Nathan Fontenot
2017-11-27 19:52 ` Michael Bringmann
2017-11-16 17:51 ` [PATCH V2 2/3] postmigration/memory: Review assoc lookup array changes Michael Bringmann
2017-11-16 17:51 ` [PATCH V2 3/3] postmigration/memory: Associativity & ibm,dynamic-memory-v2 Michael Bringmann
2017-11-20 16:14 ` Nathan Fontenot
2017-11-27 19:53 ` Michael Bringmann
2017-11-28 22:30 ` 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=e9689260-c088-9fd7-3883-0bd8cfed744d@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).