Re: Detecting NUMA per pmem

Hi Ross Thanks for the speedy reply. I am also adding the public list to this thread as you suggested. We have tried to dump the SPA table and this is what we get: /* * Intel ACPI Component Architecture * AML/ASL+ Disassembler version 20160108-64 * Copyright (c) 2000 - 2016 Intel Corporation * * Disassembly of NFIT, Sun Oct 22 10:46:19 2017 * * ACPI Data Table [NFIT] * * Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue */ [000h 0000 4] Signature : "NFIT" [NVDIMM Firmware Interface Table] [004h 0004 4] Table Length : 00000028 [008h 0008 1] Revision : 01 [009h 0009 1] Checksum : B2 [00Ah 0010 6] Oem ID : "SUPERM" [010h 0016 8] Oem Table ID : "SMCI--MB" [018h 0024 4] Oem Revision : 00000001 [01Ch 0028 4] Asl Compiler ID : " " [020h 0032 4] Asl Compiler Revision : 00000001 [024h 0036 4] Reserved : 00000000 Raw Table Data: Length 40 (0x28) 0000: 4E 46 49 54 28 00 00 00 01 B2 53 55 50 45 52 4D // NFIT(.....SUPERM 0010: 53 4D 43 49 2D 2D 4D 42 01 00 00 00 01 00 00 00 // SMCI--MB........ 0020: 01 00 00 00 00 00 00 00 As you can see the memory region info is missing. This specific check was done on a supermicro server. We also performed a bios update but the results were the same. As said before ,the pmem devices are detected correctly and we verified that they correspond to different numa nodes using the PCM utility.However, linux still reports both pmem devices to be on the same numa - Numa 0. If this information is missing, why pmem devices and address ranges are still detected correctly?

Is there another table that we need to check?