Hi, This new version drops all the NVDIMM related changes from the previous iteraction after the reviews done in the kernel mailing list [1]. FORM2 will not use ibm,associativity-reference-points to determine a second NUMA mode for different operation modes of PAPR-SCM.
[1] https://lore.kernel.org/linuxppc-dev/20210628151117.545935-1-aneesh.ku...@linux.ibm.com/ changes from v2: - patch 3: * reworded commit msg and comments to reflect the current state of the specification - patches 5 and 6: removed - v2 link: https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg04056.html changes from v1: - patches 1 and 2: switched places - patch 3: folded into patch 2 - patch 2: * only make CAS related changes when using the newest machine version - patch 3 (former 4): * only advertise FORM2 support for the newest machine version - patches 5 and 6 (former 6 and 7): * detect if 'device-node' was set in the command line, and if not, use the 'node' value when writing in the device tree v1 link: https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg03617.html Daniel Henrique Barboza (5): spapr_numa.c: split FORM1 code into helpers spapr: move NUMA data init to post-CAS spapr_numa.c: base FORM2 NUMA affinity support spapr: simplify spapr_numa_associativity_init params spapr: move memory/cpu less check to spapr_numa_FORM1_affinity_init() hw/ppc/spapr.c | 60 ++++------ hw/ppc/spapr_hcall.c | 4 + hw/ppc/spapr_numa.c | 224 +++++++++++++++++++++++++++++++++--- include/hw/ppc/spapr.h | 1 + include/hw/ppc/spapr_numa.h | 3 +- include/hw/ppc/spapr_ovec.h | 1 + 6 files changed, 236 insertions(+), 57 deletions(-) -- 2.31.1