[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH v3 8/9] xen/x86: add detection of memory interleaves for different nodes


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Wei Chen <wei.chen@xxxxxxx>
  • Date: Wed, 11 May 2022 09:46:38 +0800
  • Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dmarc=[1,1,header.from=arm.com])
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 40.67.248.234) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=none (message not signed); arc=none
  • Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Oq8z5BQ/mKL1DPmKTInyHTA5bNRXdCnGU2Y2WkTA6Sw=; b=A52DrO1Xik5qegCDhLqoKbjtKBW1/th3zYhH/ucVY3VOAhw97aLFbOWHGVfTSyb0UZl1un3uhUJCIzTUE7XY6TzYVwSa3ORcdJusPKXynS/04IwRRW4TC/o6Y1xagZD8d/DvI2RjDEznk6Ofyr2RIVHziHtk5aTIAIITXCf3azafd/tx4NhW/5FbyOCFozAPk6y6q6kwrbccx8GlG6l3Fm8mKp3iccqWBeM/TbVhytUHymfgQ39DOCBm1+UdS8hFKJQ7GWxoaUzHqECEs0IOlyU4eLV56tZ1mnrs2MCuQogTYeiH3bEnANULm/HqAtujETotlsvUwjXlr7ZVYm+H1A==
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Oq8z5BQ/mKL1DPmKTInyHTA5bNRXdCnGU2Y2WkTA6Sw=; b=T6vbOtBaH+T/afHD6LUTkz8eqjfW7npbPT81mya+l/dG/RFIN7p063+bbokB2eEedyEnpQk4vDohIIjxWXoZ/pcy7Eua5/C133skTn/IgAYnniO9EKILP2GG7UQvPXq6sHw255pI/wg4uCj5qipvlu1vEIbxwGWBhSdjot5VWVf+rO8D+E/1QtWr440tgMFa+xwx8JqXMVOq5faAcBx++Vax4bFqW7NGnQ2MR+oUAaw5UCOCG3wvngtxUckWq+I8E4u9cUp1DLNzwPJMs5Y3Q9pPOoNyEINWROabQSVNgx9hihBmY940TWT5JdEw3fIENs3zO5kSNUcBTzxN03RgCg==
  • Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=oV5j7ZYIkeRVvk11DYaw0fTklNgsogFNxhOf4/XHTIn5JzS7593K5t6thKKqowa4OVmJkuFTZwRA5rEFaLtZrFpXasgrDlwAHw26zodjoRMLhVu6/UjylJwAts+pNE1JZ+/rckJgyaoh9RWCtyI3Vy+Fkm3UJIDg+OkW+GAasg2m/Xex/hCC+CHJV4y2bTa9QYMzycrV0+Rvb+pyJAGOip3RTUmFtd9Lk+Az1IVZJRmNqhc8r+bKr+zWZ9Pe9yj2oaOYU/Of339TbPUkofOxbeoc5COkA/5A4Q2XJh8tNh1+Gx/PFVKPD1RRvGJshP6R8vuNBbNOATeZF7Hq2nWPmA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fDzO566/WTtwdBvlANSZRebPv1+1MfOEznij5Cl4ycuMWMyRbzMjBvRN4O90ETdSXNJ68u0g5X5HSS3PnMYAZ23HlfbBCxX8W1d2VvZPWR2GPIODqFZ8PNIFFn0AOO6Ckbtw6W9x/xO9w0idMeqcf1BYDFZyWID3pn7KnSHKUJ/sVc1XKpquo7RYXpCayEzpkgZvuiUIY8hCmUwraM5uN0jRBJX5NHJs5aXOTUbleZrOoXBqwnvAwxunSII5+571lDV3EWdn+UjQij+1Q6PAd5LzqwAFfP+WL3DfegeLYoMJtloZlkD2SVTre+j5zmNHld/qKwnacHUIxqoeGEGHXg==
  • Cc: <nd@xxxxxxx>, Wei Chen <wei.chen@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Jiamei Xie <jiamei.xie@xxxxxxx>
  • Delivery-date: Wed, 11 May 2022 01:47:33 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true

One NUMA node may contain several memory blocks. In current Xen
code, Xen will maintain a node memory range for each node to cover
all its memory blocks. But here comes the problem, in the gap of
one node's two memory blocks, if there are some memory blocks don't
belong to this node (remote memory blocks). This node's memory range
will be expanded to cover these remote memory blocks.

One node's memory range contains other nodes' memory, this is
obviously not very reasonable. This means current NUMA code only
can support node has no interleaved memory blocks. However, on a
physical machine, the addresses of multiple nodes can be interleaved.

So in this patch, we add code to detect memory interleaves of
different nodes. NUMA initialization will be failed and error
messages will be printed when Xen detect such hardware configuration.

Signed-off-by: Wei Chen <wei.chen@xxxxxxx>
Tested-by: Jiamei Xie <jiamei.xie@xxxxxxx>
---
v2 -> v3:
1. Merge the check code from a separate function to
   conflicting_memblks. This will reduce the loop
   times of node memory blocks.
2. Use an enumeration to indicate conflict check status.
3. Use a pointer to get conflict memory block id.
v1 -> v2:
1. Update the description to say we're after is no memory
   interleaves of different nodes.
2. Only update node range when it passes the interleave check.
3. Don't use full upper-case for "node".
---
 xen/arch/x86/srat.c | 115 +++++++++++++++++++++++++++++++++-----------
 1 file changed, 86 insertions(+), 29 deletions(-)

diff --git a/xen/arch/x86/srat.c b/xen/arch/x86/srat.c
index 8ffe43bdfe..53835ae3eb 100644
--- a/xen/arch/x86/srat.c
+++ b/xen/arch/x86/srat.c
@@ -42,6 +42,12 @@ static struct node node_memblk_range[NR_NODE_MEMBLKS];
 static nodeid_t memblk_nodeid[NR_NODE_MEMBLKS];
 static __initdata DECLARE_BITMAP(memblk_hotplug, NR_NODE_MEMBLKS);
 
+enum conflicts {
+       NO_CONFLICT = 0,
+       ERR_OVERLAP,
+       ERR_INTERLEAVE,
+};
+
 static inline bool node_found(unsigned idx, unsigned pxm)
 {
        return ((pxm2node[idx].pxm == pxm) &&
@@ -119,20 +125,43 @@ int valid_numa_range(paddr_t start, paddr_t end, nodeid_t 
node)
        return 0;
 }
 
-static __init int conflicting_memblks(paddr_t start, paddr_t end)
+static enum conflicts __init
+conflicting_memblks(nodeid_t nid, paddr_t start, paddr_t end,
+                   paddr_t nd_start, paddr_t nd_end, int *mblkid)
 {
        int i;
 
+       /*
+        * Scan all recorded nodes' memory blocks to check conflicts:
+        * Overlap or interleave.
+        */
        for (i = 0; i < num_node_memblks; i++) {
                struct node *nd = &node_memblk_range[i];
+               *mblkid = i;
+
+               /* Skip 0 bytes node memory block. */
                if (nd->start == nd->end)
                        continue;
+               /*
+                * Use memblk range to check memblk overlaps, include the
+                * self-overlap case.
+                */
                if (nd->end > start && nd->start < end)
-                       return i;
+                       return ERR_OVERLAP;
                if (nd->end == end && nd->start == start)
-                       return i;
+                       return ERR_OVERLAP;
+               /*
+                * Use node memory range to check whether new range contains
+                * memory from other nodes - interleave check. We just need
+                * to check full contains situation. Because overlaps have
+                * been checked above.
+                */
+               if (nid != memblk_nodeid[i] &&
+                   (nd_start < nd->start && nd->end < nd_end))
+                       return ERR_INTERLEAVE;
        }
-       return -1;
+
+       return NO_CONFLICT;
 }
 
 static __init void cutoff_node(int i, paddr_t start, paddr_t end)
@@ -275,6 +304,9 @@ acpi_numa_processor_affinity_init(const struct 
acpi_srat_cpu_affinity *pa)
 void __init
 acpi_numa_memory_affinity_init(const struct acpi_srat_mem_affinity *ma)
 {
+       enum conflicts status;
+       struct node *nd;
+       paddr_t nd_start, nd_end;
        paddr_t start, end;
        unsigned pxm;
        nodeid_t node;
@@ -310,42 +342,67 @@ acpi_numa_memory_affinity_init(const struct 
acpi_srat_mem_affinity *ma)
                bad_srat();
                return;
        }
+
+       /*
+        * For the node that already has some memory blocks, we will
+        * expand the node memory range temporarily to check memory
+        * interleaves with other nodes. We will not use this node
+        * temp memory range to check overlaps, because it will mask
+        * the overlaps in same node.
+        *
+        * Node with 0 bytes memory doesn't need this expandsion.
+        */
+       nd_start = start;
+       nd_end = end;
+       nd = &nodes[node];
+       if (nd->start != nd->end) {
+               if (nd_start > nd->start)
+                       nd_start = nd->start;
+
+               if (nd_end < end)
+                       nd_end = nd->end;
+       }
+
        /* It is fine to add this area to the nodes data it will be used later*/
-       i = conflicting_memblks(start, end);
-       if (i < 0)
-               /* everything fine */;
-       else if (memblk_nodeid[i] == node) {
-               bool mismatch = !(ma->flags & ACPI_SRAT_MEM_HOT_PLUGGABLE) !=
-                               !test_bit(i, memblk_hotplug);
-
-               printk("%sSRAT: PXM %u (%"PRIpaddr"-%"PRIpaddr") overlaps with 
itself (%"PRIpaddr"-%"PRIpaddr")\n",
-                      mismatch ? KERN_ERR : KERN_WARNING, pxm, start, end,
-                      node_memblk_range[i].start, node_memblk_range[i].end);
-               if (mismatch) {
+       status = conflicting_memblks(node, start, end, nd_start, nd_end, &i);
+       if (status == ERR_OVERLAP) {
+               if (memblk_nodeid[i] == node) {
+                       bool mismatch = !(ma->flags &
+                                       ACPI_SRAT_MEM_HOT_PLUGGABLE) !=
+                                       !test_bit(i, memblk_hotplug);
+
+                       printk("%sSRAT: PXM %u (%"PRIpaddr"-%"PRIpaddr") 
overlaps with itself (%"PRIpaddr"-%"PRIpaddr")\n",
+                              mismatch ? KERN_ERR : KERN_WARNING, pxm, start,
+                              end, node_memblk_range[i].start,
+                              node_memblk_range[i].end);
+                       if (mismatch) {
+                               bad_srat();
+                               return;
+                       }
+               } else {
+                       printk(KERN_ERR
+                              "SRAT: PXM %u (%"PRIpaddr"-%"PRIpaddr") overlaps 
with PXM %u (%"PRIpaddr"-%"PRIpaddr")\n",
+                              pxm, start, end, node_to_pxm(memblk_nodeid[i]),
+                              node_memblk_range[i].start,
+                              node_memblk_range[i].end);
                        bad_srat();
                        return;
                }
-       } else {
+       } else if (status == ERR_INTERLEAVE) {
                printk(KERN_ERR
-                      "SRAT: PXM %u (%"PRIpaddr"-%"PRIpaddr") overlaps with 
PXM %u (%"PRIpaddr"-%"PRIpaddr")\n",
-                      pxm, start, end, node_to_pxm(memblk_nodeid[i]),
+                      "SRAT: Node %u: (%"PRIpaddr"-%"PRIpaddr") interleaves 
with node %u memblk (%"PRIpaddr"-%"PRIpaddr")\n",
+                      node, nd_start, nd_end, memblk_nodeid[i],
                       node_memblk_range[i].start, node_memblk_range[i].end);
                bad_srat();
                return;
        }
-       if (!(ma->flags & ACPI_SRAT_MEM_HOT_PLUGGABLE)) {
-               struct node *nd = &nodes[node];
 
-               if (!node_test_and_set(node, memory_nodes_parsed)) {
-                       nd->start = start;
-                       nd->end = end;
-               } else {
-                       if (start < nd->start)
-                               nd->start = start;
-                       if (nd->end < end)
-                               nd->end = end;
-               }
+       if (!(ma->flags & ACPI_SRAT_MEM_HOT_PLUGGABLE)) {
+               node_set(node, memory_nodes_parsed);
+               nd->start = nd_start;
+               nd->end = nd_end;
        }
+
        printk(KERN_INFO "SRAT: Node %u PXM %u %"PRIpaddr"-%"PRIpaddr"%s\n",
               node, pxm, start, end,
               ma->flags & ACPI_SRAT_MEM_HOT_PLUGGABLE ? " (hotplug)" : "");
-- 
2.25.1




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.