From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Michael Ellerman <mpe@ellerman.id.au>,
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 0/3] powerpc/hotplug: Fix affinity assoc for LPAR migration
Date: Thu, 2 Nov 2017 15:52:45 -0500 [thread overview]
Message-ID: <eef99211-b3a2-41cc-f4a1-8a88878c9e12@linux.vnet.ibm.com> (raw)
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 are intended to recognize changes to that associativity
as represented by various device-tree properties, and generate calls
to other code layers to reset the associativity of the blocks and any
other related data structures.
Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Michael Bringmann (3):
powerpc/hotplug/memory: Apply assoc mem updates from 'ibm,dynamic-memory' Post LPAR Migration
powerpc/hotplug/memory: Apply assoc lookup array updates Post Migration Topo
powerpc/hotplug/memory: Apply assoc mem updates from 'ibm,dynamic-memory-v2' Post LPAR Migration
next reply other threads:[~2017-11-02 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 20:52 Michael Bringmann [this message]
2017-11-02 20:53 ` [PATCH 1/3] hotplug/memory: Apply assoc mem updates Post Migration Topo Michael Bringmann
2017-11-02 20:53 ` [PATCH 2/3] postmigration/memory: Review assoc lookup array changes Michael Bringmann
2017-11-02 20:53 ` [PATCH 3/3] postmigration/memory: Associativity & ibm,dynamic-memory-v2 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=eef99211-b3a2-41cc-f4a1-8a88878c9e12@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®