On Wed, May 08, 2024 at 01:02:52PM +0100, Jonathan Cameron wrote: > > > [ 0.000000] ACPI: SRAT: Node 0 PXM 0 [mem 0x40000000-0xbfffffff] > > [ 0.000000] ACPI: SRAT: Node 1 PXM 1 [mem 0xc0000000-0x13fffffff] > > [ 0.000000] ACPI: Unknown target node for memory at 0x10000000000, > > assuming node 0 > > [ 0.000000] NUMA: Warning: invalid memblk node 16 [mem > > 0x0000000004000000-0x0000000007ffffff] > > [ 0.000000] NUMA: Faking a node at [mem > > 0x0000000004000000-0x000000013fffffff] > > [ 0.000000] NUMA: NODE_DATA [mem 0x13f7f89c0-0x13f7fafff] > > > > Previous discussion: > > https://lore.kernel.org/linux-cxl/20231011150620.00002...@huawei.com/ > > > > root@debian-bullseye-arm64:~# cxl create-region -d decoder0.0 -t ram > > [ 68.653873] cxl region0: Bypassing cpu_cache_invalidate_memregion() for > > testing! > > [ 68.660568] Unknown target node for memory at 0x10000000000, assuming > > node 0 > > You need a load of kernel changes for NUMA nodes to work correctly with > CXL memory on arm64 platforms. I have some working code but need to tidy > up a few corners that came up in an internal review earlier this week. > > I have some travel coming up so may take a week or so to get those out. > > Curiously that invalid memblk has nothing to do with the CXL fixed memory > window > Could you check if that is happening for you without the CXL patches? >
Thanks. I have checked it, the problem is caused by my bios firmware file. I change the bios file and the numa topology can works. BTW, if it is convenient, could you help to post the link of the patches of CXL memory NUMA nodes on arm64 platforms? > > Whilst it doesn't work yet (because of missing kernel support) > you'll need something that looks more like the generic ports test added in > https://gitlab.com/jic23/qemu/-/commit/6589c527920ba22fe0923b60b58d33a8e9fd371e > > Most importantly > -numa node,nodeid=2 -object acpi-generic-port,id=gp0,pci-bus-cxl.1,node=2 > + the bits setting distances etc. Note CXL memory does not provide SLIT like > data at the moment, so the test above won't help you identify if it is > correctly > set up. That's a gap in general in the kernel support. Whilst we'd love > it if everyone moved to hmat derived information we may need to provide > some fallback. > > Jonathan > Many thanks Yuquan
