[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210927064119.127285-1-gshan@redhat.com>
Date: Mon, 27 Sep 2021 14:41:17 +0800
From: Gavin Shan <gshan@...hat.com>
To: devicetree@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
robh@...nel.org, maz@...nel.org, rdunlap@...radead.org,
catalin.marinas@....com, will@...nel.org, shan.gavin@...il.com
Subject: [PATCH v2 0/2] Specify empty NUMA node
There are multiple empty nodes, where no memory resides in, are allowed
in virtual machine (VM) backed by QEMU. I don't find anywhere to document
how the corresponding device nodes are populated. This series adds one
section in Documentation/devicetree/bindings/numa.txt to document how
the empty NUMA nodes are handled: no device nodes are existing for these
empty NUMA nodes, but the NUMA IDs and distance map are still valid in
"numa-distance-map-v1" compatible device node.
PATCH[1] adds one section in Documentation/devicetree/bindings/numa.txt
to specify how device nodes are populated for these empty NUMA
nodes.
PATCH[2] fetches NUMA IDs and distance maps from "numa-distance-map-v1"
compatible device node.
Changelog
=========
* No device nodes for empty NUMA nodes (Rob)
* Add patch to fetch NUMA IDs and distance map from the
"numa-distance-map-v1" compatible device node (Rob)
Gavin Shan (2):
Documentation, dt, numa: Add note to empty NUMA node
of, numa: Fetch empty NUMA node ID from distance map
Documentation/devicetree/bindings/numa.txt | 46 +++++++++++++++++++++-
drivers/of/of_numa.c | 2 +
2 files changed, 47 insertions(+), 1 deletion(-)
--
2.23.0
Powered by blists - more mailing lists