From: Andrew Jones <drjones@redhat.com>
To: Gavin Shan <gshan@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, shan.gavin@gmail.com, ehabkost@redhat.com
Subject: Re: [PATCH 2/2] hw/arm/virt: Don't create device-tree node for empty NUMA node
Date: Wed, 6 Oct 2021 12:36:43 +0200 [thread overview]
Message-ID: <20211006103643.nzavhkf367pmackx@gator.home> (raw)
In-Reply-To: <20211006102209.6989-3-gshan@redhat.com>
On Wed, Oct 06, 2021 at 06:22:09PM +0800, Gavin Shan wrote:
> The empty NUMA node, where no memory resides, are allowed. For
> example, the following command line specifies two empty NUMA nodes.
> With this, QEMU fails to boot because of the conflicting device-tree
> node names, as the following error message indicates.
>
> /home/gavin/sandbox/qemu.main/build/qemu-system-aarch64 \
> -accel kvm -machine virt,gic-version=host \
> -cpu host -smp 4,sockets=2,cores=2,threads=1 \
> -m 1024M,slots=16,maxmem=64G \
> -object memory-backend-ram,id=mem0,size=512M \
> -object memory-backend-ram,id=mem1,size=512M \
> -numa node,nodeid=0,cpus=0-1,memdev=mem0 \
> -numa node,nodeid=1,cpus=2-3,memdev=mem1 \
> -numa node,nodeid=2 \
> -numa node,nodeid=3
> :
> qemu-system-aarch64: FDT: Failed to create subnode /memory@80000000: FDT_ERR_EXISTS
>
> As specified by linux device-tree binding document, the device-tree
> nodes for these empty NUMA nodes shouldn't be generated. However,
> the corresponding NUMA node IDs should be included in the distance
> map device-tree node. This skips populating the device-tree nodes
> for these empty NUMA nodes to avoid the error, so that QEMU can be
> started successfully.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> hw/arm/boot.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
> index 57efb61ee4..4e5898fcdc 100644
> --- a/hw/arm/boot.c
> +++ b/hw/arm/boot.c
> @@ -603,6 +603,10 @@ int arm_load_dtb(hwaddr addr, const struct arm_boot_info *binfo,
> mem_base = binfo->loader_start;
> for (i = 0; i < ms->numa_state->num_nodes; i++) {
> mem_len = ms->numa_state->nodes[i].node_mem;
> + if (!mem_len) {
> + continue;
> + }
> +
> rc = fdt_add_memory_node(fdt, acells, mem_base,
> scells, mem_len, i);
> if (rc < 0) {
> --
> 2.23.0
>
Reviewed-by: Andrew Jones <drjones@redhat.com>
prev parent reply other threads:[~2021-10-06 10:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 10:22 [PATCH 0/2] hw/arm/virt: Fix qemu booting failure on device-tree Gavin Shan
2021-10-06 10:22 ` [PATCH 1/2] numa: Set default distance map if needed Gavin Shan
2021-10-06 10:35 ` Andrew Jones
2021-10-06 11:03 ` Gavin Shan
2021-10-06 11:56 ` Andrew Jones
2021-10-07 23:51 ` Gavin Shan
2021-10-08 6:07 ` Andrew Jones
2021-10-12 6:13 ` Gavin Shan
2021-10-12 9:40 ` Igor Mammedov
2021-10-12 10:31 ` Gavin Shan
2021-10-12 11:18 ` Igor Mammedov
2021-10-12 11:48 ` Andrew Jones
2021-10-12 12:34 ` Igor Mammedov
2021-10-12 13:05 ` Andrew Jones
2021-10-12 22:59 ` Gavin Shan
2021-10-12 10:37 ` Andrew Jones
2021-10-12 12:27 ` Igor Mammedov
2021-10-12 13:13 ` Andrew Jones
2021-10-12 13:53 ` Igor Mammedov
2021-10-12 23:32 ` Gavin Shan
2021-10-13 9:32 ` Igor Mammedov
2021-10-13 6:29 ` Andrew Jones
2021-10-06 10:22 ` [PATCH 2/2] hw/arm/virt: Don't create device-tree node for empty NUMA node Gavin Shan
2021-10-06 10:36 ` Andrew Jones [this message]
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=20211006103643.nzavhkf367pmackx@gator.home \
--to=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=gshan@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shan.gavin@gmail.com \
/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).