diff options
author | Oliver O'Halloran <oohall@gmail.com> | 2019-10-17 19:26:30 +1100 |
---|---|---|
committer | Oliver O'Halloran <oohall@gmail.com> | 2019-11-04 14:58:52 +1100 |
commit | 1c282887c0d58e56364a2b000c437287d08da815 (patch) | |
tree | 748dd34852497e40413287d53593970ca6dd01a1 /core/mem_region.c | |
parent | 6cf9ace9d69dcb5c37b328625132bc5c9624b778 (diff) | |
download | skiboot-1c282887c0d58e56364a2b000c437287d08da815.zip skiboot-1c282887c0d58e56364a2b000c437287d08da815.tar.gz skiboot-1c282887c0d58e56364a2b000c437287d08da815.tar.bz2 |
memory: Add NUMA associtivity information to DT
The ibm,chip-id property is not sufficent for Linux to work out the NUMA
node that a pmem region is placed on. Add any nodes that are compatible
with "pmem-region" to the pass where we add affinity information to the
normal memory@ nodes.
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Diffstat (limited to 'core/mem_region.c')
-rw-r--r-- | core/mem_region.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/core/mem_region.c b/core/mem_region.c index 47d7544..06cef1b 100644 --- a/core/mem_region.c +++ b/core/mem_region.c @@ -1068,7 +1068,8 @@ void mem_region_init(void) * done by add_chip_dev_associativity() */ dt_for_each_node(dt_root, i) { - if (!dt_has_node_property(i, "device_type", "memory")) + if (!dt_has_node_property(i, "device_type", "memory") && + !dt_has_node_property(i, "compatible", "pmem-region")) continue; /* Add associativity properties */ |