Update memory dlpar for dynamic reconfiguration memory
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest5 patches 1 replyIn review
- v15 patches 4 repliesSuperseded
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | Allow phandle to be specified in formats other than decimalarch/ | +0 | 0 replies | |
| 2/5 | Use base address to derive starting page frame numberarch/ | +0 | 0 replies | |
| 3/5 | Update the device tree correctly for drconf memory add/removearch/ arch/ include/ | +4 | 0 replies | |
| 4/5 | Split code into helper routines for drconf memoryarch/ | +0 | 1 reply | |
| 5/5 | Update numa association of hotplug memory add for drconf memoryarch/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH 0/5 v2] Update memory dlpar for dynamic reconfiguration memory
The following patchset corrects a set of issues for memory dlpar and the representation of memory in the device tree under the ibm,dynamic-reconfiguration-memory node.
On newer hardware and kernels, the device tree has changed so that all memory appears under the ibm,dynamic-reconfiguration-memory node in the device tree. This node has several properties that describe all possible lmbs, lmb-size and numa affinity.
The ibm,dynamic-memory property is a list of all possible lmbs, where each list entry contains the base address, drc index, associativity array index and a set of flags.
The ibm,associativity-lookup-arrays property contains a list of associativity arrays and the ibm,lmb-size property contains the size of the lmbs
For reference, each lmb available to the system was previously represented with a node in the device tree, of the form /proc/device-tree/memory@XXXXXXXX. Each of these memory nodes had properties such as "ibm,my-drc-index" for the
drc index and "regs" which contained the base address and lmb size of the lmb.
With the new device tree layout, code associated with memory dlpar needs to be updated to parse the new device tree layout and properly call the memory hotplug notifier chains. Additionally, numa associativity done during hotplug add of memory needs an update for parsing the new device tree layout.