From: Gavin Shan <email@example.com>
To: Rob Herring <firstname.lastname@example.org>
"open list:KERNEL VIRTUAL MACHINE FOR ARM64 (KVM/arm64)"
<email@example.com>, Marc Zyngier <firstname.lastname@example.org>,
Randy Dunlap <email@example.com>,
Catalin Marinas <firstname.lastname@example.org>,
Will Deacon <email@example.com>,
Subject: Re: [PATCH v2 2/2] of, numa: Fetch empty NUMA node ID from distance map
Date: Wed, 29 Sep 2021 12:00:31 +1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 9/29/21 3:22 AM, Rob Herring wrote:
> On Mon, Sep 27, 2021 at 6:59 PM Gavin Shan <email@example.com> wrote:
>> On 9/28/21 12:49 AM, Rob Herring wrote:
>>> On Mon, Sep 27, 2021 at 1:42 AM Gavin Shan <firstname.lastname@example.org> wrote:
>>>> There is no device node for the empty NUMA node. However, the
>>>> corresponding NUMA node ID and distance map is still valid in
>>>> "numa-distance-map-v1" compatible device node.
>>>> This fetches the NUMA node ID and distance map for these empty
>>>> NUMA node from "numa-distance-map-v1" compatible device node.
>>> This is much nicer.
>> Indeed, thanks for your suggestions :)
>>>> Signed-off-by: Gavin Shan <email@example.com>
>>>> drivers/of/of_numa.c | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>> diff --git a/drivers/of/of_numa.c b/drivers/of/of_numa.c
>>>> index fe6b13608e51..5949829a1b00 100644
>>>> --- a/drivers/of/of_numa.c
>>>> +++ b/drivers/of/of_numa.c
>>>> @@ -111,6 +111,8 @@ static int __init of_numa_parse_distance_map_v1(struct device_node *map)
>>>> return -EINVAL;
>>>> + node_set(nodea, numa_nodes_parsed);
>>> With this, couldn't we remove of_numa_parse_cpu_nodes() as the only
>>> thing it does is node_set()?
>> I don't think so for couple of reasons:
>> (1) With problematic device-tree, the distance map node might be missed
>> or incomplete. In this case, of_numa_parse_cpu_nodes() still helps.
> It's not the kernel's job to validate the DT (if it was, it is doing a
> terrible job). I would suggest writing some checks for dtc if we're
> worried about correctness. (The schemas don't work too well for cross
> node checks.)
I didn't look into dtc's code and not sure if dtc has this sort of validation.
Besides, dtc is out of scope when QEMU is involved. The device-tree blob isn't
produced by dtc in QEMU.
>> (2) @numa_nodes_parsed is also updated when the memory nodes are iterated
>> in of_numa_parse_memory_nodes() and numa_add_memblk().
>> So @numa_nodes_parsed, which is synchronized to @node_possible_map afterwards,
>> is the gathering output of CPU nodes, memory nodes and distance map node.
> Is it valid to have node id's that are not in the distance map?
Yes, it's valid from the kernel's perspective. The default distance
matrix, where the local and remote distances are 10 and 20, is applied
if the distance map is missed in device-tree. The code can be found from
Besides, it's possible that the distance map isn't populated by QEMU.
However, I'm going to improve the situation so the distance map will
be populated unconditionally.
The following option is supported by QEMU, to specify the distance
between two NUMA nodes. However, it's not mandatory. The distance
map in device-tree won't be populated if the option is missed.
next prev parent reply other threads:[~2021-09-29 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 6:41 [PATCH v2 0/2] Specify empty NUMA node Gavin Shan
2021-09-27 6:41 ` [PATCH v2 1/2] Documentation, dt, numa: Add note to " 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 [this message]
2021-10-04 18:13 ` Rob Herring
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).