From: Gavin Shan <gshan@redhat.com>
To: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, robh@kernel.org, maz@kernel.org,
rdunlap@infradead.org, catalin.marinas@arm.com, will@kernel.org,
shan.gavin@gmail.com
Subject: [PATCH v2 0/2] Specify empty NUMA node
Date: Mon, 27 Sep 2021 14:41:17 +0800 [thread overview]
Message-ID: <20210927064119.127285-1-gshan@redhat.com> (raw)
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
next reply other threads:[~2021-09-27 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 6:41 Gavin Shan [this message]
2021-09-27 6:41 ` [PATCH v2 1/2] Documentation, dt, numa: Add note to empty NUMA node Gavin Shan
2021-10-04 18:13 ` Rob Herring
2021-09-27 6:41 ` [PATCH v2 2/2] of, numa: Fetch empty NUMA node ID from distance map Gavin Shan
2021-09-27 14:49 ` Rob Herring
2021-09-27 23:59 ` Gavin Shan
2021-09-28 17:22 ` Rob Herring
2021-09-29 2:00 ` Gavin Shan
2021-10-04 18:13 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210927064119.127285-1-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=shan.gavin@gmail.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).