From: Wei Chen <wei.c...@arm.com>
The NUMA information provided in the host Device-Tree
are only for Xen. For dom0, we want to hide them as they
may be different (for now, dom0 is still not aware of NUMA)
The CPU and memory nodes are recreated from scratch for the
domain. So we already skip the "numa-node-id" property for
these two types of nodes.
However, some devices like PCIe may have "numa-node-id"
property too. We have to skip them as well.
Signed-off-by: Wei Chen <wei.c...@arm.com>
Signed-off-by: Henry Wang <henry.w...@arm.com>
Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>
---
v2 -> v3:
1. No change.
v1 -> v2:
1. Add Rb
---
xen/arch/arm/domain_build.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index f80fdd1af2..2bf586fc45 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -1185,6 +1185,10 @@ static int __init write_properties(struct domain *d,
struct kernel_info *kinfo,
continue;
}
+ /* Dom0 is currently NUMA unaware */
+ if ( dt_property_name_is_equal(prop, "numa-node-id") )
+ continue;
+
res = fdt_property(kinfo->fdt, prop->name, prop_data, prop_len);
if ( res )
@@ -2567,6 +2571,8 @@ static int __init handle_node(struct domain *d, struct
kernel_info *kinfo,
DT_MATCH_TYPE("memory"),
/* The memory mapped timer is not supported by Xen. */
DT_MATCH_COMPATIBLE("arm,armv7-timer-mem"),
+ /* Numa info doesn't need to be exposed to Domain-0 */
+ DT_MATCH_COMPATIBLE("numa-distance-map-v1"),
{ /* sentinel */ },
};
static const struct dt_device_match timer_matches[] __initconst =
--
2.25.1
