Closing the Xen dom0 I/O Gap with NUMA Awareness
Making Xen's dom0 I/O path NUMA aware
I fixed a critical gap where dom0 memory was skewed toward low-address nodes on multi-socket hosts. By implementing proportional memory allocation and synthesizing accurate SRAT, SLIT, and x2APIC topology data, dom0 now sees the real hardware layout. This ensures that even unsandboxed containers running directly in dom0 benefit from proper NUMA balancing, preventing performance regressions when adopting Xen.
A non-Edera pod could end up slower on an Edera host than it had been on the same box as plain Linux, purely because turning the machine into a Xen dom0 hid the topology its workloads used to see.