From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, mwb@linux.vnet.ibm.com
Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Juliet Kim <minkim@us.ibm.com>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Subject: [PATCH v03 0/5] powerpc/migration: Affinity fix for memory
Date: Mon, 01 Oct 2018 07:59:19 -0500 [thread overview]
Message-ID: <20181001125846.2676.89826.stgit@ltcalpine2-lp9.aus.stglabs.ibm.com> (raw)
The migration of LPARs across Power systems affects many attributes
including that of the associativity of memory blocks. 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 recorded in
internal data structures when compared to the latest copies in
the device tree (e.g. ibm,dynamic-memory, ibm,dynamic-memory-v2).
* 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 memory.
* Re-register the 'changed' entities into the target system.
Re-registration of memory blocks mostly entails acting as if they
have been newly hot-added into the target system.
This code builds upon features introduced in a previous patch set
that updates CPUs for affinity changes that may occur during LPM.
Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Michael Bringmann (5):
powerpc/drmem: Export 'dynamic-memory' loader
powerpc/drmem: Add internal_flags feature
migration/memory: Add hotplug flags READD_MULTIPLE
migration/memory: Evaluate LMB assoc changes
migration/memory: Support 'ibm,dynamic-memory-v2'
---
Changes in v03:
-- Change operation to tag changed LMBs in DRMEM array instead
of queuing a potentially huge number of structures.
-- Added another hotplug queue event for CPU/memory operations
-- Added internal_flags feature to DRMEM
-- Improve the patch description language for the patch set.
-- Revise patch set to queue worker for memory association
updates directly to pseries worker queue.
next reply other threads:[~2018-10-01 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 12:59 Michael Bringmann [this message]
2018-10-01 12:59 ` [PATCH v03 1/5] powerpc/drmem: Export 'dynamic-memory' loader Michael Bringmann
2018-10-02 20:56 ` Tyrel Datwyler
2018-10-03 13:22 ` Michael Bringmann
2018-10-03 1:00 ` Michael Ellerman
2018-10-04 2:24 ` Nathan Fontenot
2018-10-09 11:19 ` Michael Ellerman
2018-10-01 12:59 ` [PATCH v03 2/5] powerpc/drmem: Add internal_flags feature Michael Bringmann
2018-10-01 12:59 ` [PATCH v03 3/5] migration/memory: Add hotplug READD_MULTIPLE Michael Bringmann
2018-10-02 21:03 ` Tyrel Datwyler
2018-10-03 13:31 ` Michael Bringmann
2018-10-01 13:00 ` [PATCH v03 4/5] migration/memory: Evaluate LMB assoc changes Michael Bringmann
2018-10-02 21:08 ` Tyrel Datwyler
2018-10-03 14:21 ` Michael Bringmann
2018-10-01 13:00 ` [PATCH v03 5/5] migration/memory: Support '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=20181001125846.2676.89826.stgit@ltcalpine2-lp9.aus.stglabs.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minkim@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.