From: Rob Herring <robh@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: devicetree@vger.kernel.org, linux-efi@vger.kernel.org,
maz@kernel.org, rdunlap@infradead.org,
linux-kernel@vger.kernel.org, shan.gavin@gmail.com,
catalin.marinas@arm.com, will@kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] Documentation, dt, numa: Add note to empty NUMA node
Date: Mon, 4 Oct 2021 13:13:38 -0500 [thread overview]
Message-ID: <YVtEUpIFdOrIoH0B@robh.at.kernel.org> (raw)
In-Reply-To: <20210927064119.127285-2-gshan@redhat.com>
On Mon, 27 Sep 2021 14:41:18 +0800, Gavin Shan wrote:
> The empty memory nodes, where no memory resides in, are allowed.
> The NUMA node IDs are still valid and parsed, but memory may be
> added to them through hotplug afterwards. Currently, QEMU fails
> to boot when multiple empty memory nodes are specified. It's
> caused by device-tree population failure and duplicated memory
> node names.
>
> The device-tree specification doesn't provide how empty NUMA
> nodes are handled. Besides, I finds difficulty to get where
> this case is documented. So lets add a section for empty memory
> nodes to cover it in NUMA binding document.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> Documentation/devicetree/bindings/numa.txt | 46 +++++++++++++++++++++-
> 1 file changed, 45 insertions(+), 1 deletion(-)
>
Applied, thanks!
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: devicetree@vger.kernel.org, catalin.marinas@arm.com,
shan.gavin@gmail.com, will@kernel.org, rdunlap@infradead.org,
maz@kernel.org, linux-efi@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation, dt, numa: Add note to empty NUMA node
Date: Mon, 4 Oct 2021 13:13:38 -0500 [thread overview]
Message-ID: <YVtEUpIFdOrIoH0B@robh.at.kernel.org> (raw)
In-Reply-To: <20210927064119.127285-2-gshan@redhat.com>
On Mon, 27 Sep 2021 14:41:18 +0800, Gavin Shan wrote:
> The empty memory nodes, where no memory resides in, are allowed.
> The NUMA node IDs are still valid and parsed, but memory may be
> added to them through hotplug afterwards. Currently, QEMU fails
> to boot when multiple empty memory nodes are specified. It's
> caused by device-tree population failure and duplicated memory
> node names.
>
> The device-tree specification doesn't provide how empty NUMA
> nodes are handled. Besides, I finds difficulty to get where
> this case is documented. So lets add a section for empty memory
> nodes to cover it in NUMA binding document.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> Documentation/devicetree/bindings/numa.txt | 46 +++++++++++++++++++++-
> 1 file changed, 45 insertions(+), 1 deletion(-)
>
Applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: devicetree@vger.kernel.org, catalin.marinas@arm.com,
shan.gavin@gmail.com, will@kernel.org, rdunlap@infradead.org,
maz@kernel.org, linux-efi@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation, dt, numa: Add note to empty NUMA node
Date: Mon, 4 Oct 2021 13:13:38 -0500 [thread overview]
Message-ID: <YVtEUpIFdOrIoH0B@robh.at.kernel.org> (raw)
In-Reply-To: <20210927064119.127285-2-gshan@redhat.com>
On Mon, 27 Sep 2021 14:41:18 +0800, Gavin Shan wrote:
> The empty memory nodes, where no memory resides in, are allowed.
> The NUMA node IDs are still valid and parsed, but memory may be
> added to them through hotplug afterwards. Currently, QEMU fails
> to boot when multiple empty memory nodes are specified. It's
> caused by device-tree population failure and duplicated memory
> node names.
>
> The device-tree specification doesn't provide how empty NUMA
> nodes are handled. Besides, I finds difficulty to get where
> this case is documented. So lets add a section for empty memory
> nodes to cover it in NUMA binding document.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> Documentation/devicetree/bindings/numa.txt | 46 +++++++++++++++++++++-
> 1 file changed, 45 insertions(+), 1 deletion(-)
>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-04 18:13 UTC|newest]
Thread overview: 27+ 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 ` Gavin Shan
2021-09-27 6:41 ` Gavin Shan
2021-09-27 6:41 ` [PATCH v2 1/2] Documentation, dt, numa: Add note to " Gavin Shan
2021-09-27 6:41 ` Gavin Shan
2021-09-27 6:41 ` Gavin Shan
2021-10-04 18:13 ` Rob Herring [this message]
2021-10-04 18:13 ` Rob Herring
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 6:41 ` Gavin Shan
2021-09-27 6:41 ` Gavin Shan
2021-09-27 14:49 ` Rob Herring
2021-09-27 14:49 ` Rob Herring
2021-09-27 14:49 ` Rob Herring
2021-09-27 23:59 ` Gavin Shan
2021-09-27 23:59 ` Gavin Shan
2021-09-27 23:59 ` Gavin Shan
2021-09-28 17:22 ` Rob Herring
2021-09-28 17:22 ` Rob Herring
2021-09-28 17:22 ` Rob Herring
2021-09-29 2:00 ` Gavin Shan
2021-09-29 2:00 ` Gavin Shan
2021-09-29 2:00 ` Gavin Shan
2021-10-04 18:13 ` Rob Herring
2021-10-04 18:13 ` Rob Herring
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=YVtEUpIFdOrIoH0B@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gshan@redhat.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.