On 17.04.2025 10:53, Andrew Cooper wrote: > This seems to have been quite an oversite in Xen's NUMA support, albeit it
Nit: oversight? > probably because NUMA was arch-specific at first. > > Take the opportunity to sort the includes. > > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> Reviewed-by: Jan Beulich <jbeul...@suse.com> > For the !NUMA case, cpu_to_node() defaults to 0 rather than NUMA_NO_NODE, > making memflags nonzero. I'm not sure how wise this is, but ARM runs seem > happy with it. As to Arm: May be worth noting in the commit message that this is unlikely to have any useful effect when SEPARATE_XENHEAP=y. I guess our only option to address that (if any Arm32 NUMA systems exist) would be to use vmap(). Jan
