From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Andrew Jones <drjones@redhat.com>
Cc: peter.maydell@linaro.org, david.daney@cavium.com,
peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH v5 3/5] ARM: Add numa-node-id for /memory node
Date: Sat, 23 Apr 2016 16:02:53 +0800 [thread overview]
Message-ID: <571B2C2D.1070806@huawei.com> (raw)
In-Reply-To: <20160423074542.xhwqjwfaq74kt7br@hawk.localdomain>
On 2016/4/23 15:45, Andrew Jones wrote:
>>>> @@ -456,14 +460,39 @@ static int load_dtb(hwaddr addr, const struct arm_boot_info *binfo,
>>>> > >> goto fail;
>>>> > >> }
>>>> > >>
>>>> > >> + mem_len = (nb_numa_nodes > 0) ? numa_info[0].node_mem : binfo->ram_size;
>>>> > >> rc = qemu_fdt_setprop_sized_cells(fdt, "/memory", "reg",
>>> > >
>>> > > So node0's memory node will still be called '/memory' instead of
>>> > > '/memory@addr' like the other nodes? Shouldn't we change it too?
>>> > >
>> > Previously I deleted the /memory node creation codes in virt.c and
>> > create here, but that will cause other boards booting fail since
>> > load_dtb() is a common function. So to avoid more changes to other
>> > files, I just use current way. So is there any way to change the node
>> > name after it's created in qemu?
> I'm not sure if that's possible, but we could maybe use qemu_fdt_nop_node
> to turn /memory into a NOP node, and then add a new one?
This would be a good solution, I think. I'll update it using
qemu_fdt_nop_node.
Thanks,
--
Shannon
WARNING: multiple messages have this Message-ID (diff)
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Andrew Jones <drjones@redhat.com>
Cc: peter.maydell@linaro.org, david.daney@cavium.com,
qemu-devel@nongnu.org, peter.huangpeng@huawei.com,
qemu-arm@nongnu.org, shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH v5 3/5] ARM: Add numa-node-id for /memory node
Date: Sat, 23 Apr 2016 16:02:53 +0800 [thread overview]
Message-ID: <571B2C2D.1070806@huawei.com> (raw)
In-Reply-To: <20160423074542.xhwqjwfaq74kt7br@hawk.localdomain>
On 2016/4/23 15:45, Andrew Jones wrote:
>>>> @@ -456,14 +460,39 @@ static int load_dtb(hwaddr addr, const struct arm_boot_info *binfo,
>>>> > >> goto fail;
>>>> > >> }
>>>> > >>
>>>> > >> + mem_len = (nb_numa_nodes > 0) ? numa_info[0].node_mem : binfo->ram_size;
>>>> > >> rc = qemu_fdt_setprop_sized_cells(fdt, "/memory", "reg",
>>> > >
>>> > > So node0's memory node will still be called '/memory' instead of
>>> > > '/memory@addr' like the other nodes? Shouldn't we change it too?
>>> > >
>> > Previously I deleted the /memory node creation codes in virt.c and
>> > create here, but that will cause other boards booting fail since
>> > load_dtb() is a common function. So to avoid more changes to other
>> > files, I just use current way. So is there any way to change the node
>> > name after it's created in qemu?
> I'm not sure if that's possible, but we could maybe use qemu_fdt_nop_node
> to turn /memory into a NOP node, and then add a new one?
This would be a good solution, I think. I'll update it using
qemu_fdt_nop_node.
Thanks,
--
Shannon
next prev parent reply other threads:[~2016-04-23 8:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 6:23 [Qemu-devel] [PATCH v5 0/5] ARM: Add NUMA support for machine virt Shannon Zhao
2016-04-21 6:23 ` Shannon Zhao
2016-04-21 6:23 ` [Qemu-arm] [PATCH v5 1/5] ARM: Virt: Add /distance-map node for NUMA Shannon Zhao
2016-04-21 6:23 ` [Qemu-devel] " Shannon Zhao
2016-04-22 12:25 ` [Qemu-arm] " Andrew Jones
2016-04-22 12:25 ` Andrew Jones
2016-04-23 1:17 ` [Qemu-arm] " Shannon Zhao
2016-04-23 1:17 ` Shannon Zhao
2016-04-23 7:03 ` [Qemu-arm] " Andrew Jones
2016-04-23 7:03 ` Andrew Jones
2016-04-23 7:27 ` [Qemu-arm] " Shannon Zhao
2016-04-23 7:27 ` Shannon Zhao
2016-04-21 6:23 ` [Qemu-devel] [PATCH v5 2/5] ARM: Virt: Set numa-node-id for CPUs Shannon Zhao
2016-04-21 6:23 ` Shannon Zhao
2016-04-22 12:34 ` [Qemu-arm] " Andrew Jones
2016-04-22 12:34 ` Andrew Jones
2016-04-21 6:23 ` [Qemu-arm] [PATCH v5 3/5] ARM: Add numa-node-id for /memory node Shannon Zhao
2016-04-21 6:23 ` [Qemu-devel] " Shannon Zhao
2016-04-22 12:48 ` [Qemu-arm] " Andrew Jones
2016-04-22 12:48 ` Andrew Jones
2016-04-23 1:16 ` [Qemu-arm] " Shannon Zhao
2016-04-23 1:16 ` Shannon Zhao
2016-04-23 7:45 ` [Qemu-arm] " Andrew Jones
2016-04-23 7:45 ` Andrew Jones
2016-04-23 8:02 ` Shannon Zhao [this message]
2016-04-23 8:02 ` Shannon Zhao
2016-04-21 6:23 ` [Qemu-devel] [PATCH v5 4/5] include/hw/acpi/acpi-defs: Add GICC Affinity Structure Shannon Zhao
2016-04-21 6:23 ` Shannon Zhao
2016-04-22 13:26 ` [Qemu-arm] " Andrew Jones
2016-04-22 13:26 ` [Qemu-devel] " Andrew Jones
2016-04-21 6:23 ` [Qemu-arm] [PATCH v5 5/5] hw/arm/virt-acpi-build: Generate SRAT table Shannon Zhao
2016-04-21 6:23 ` [Qemu-devel] " Shannon Zhao
2016-04-22 13:26 ` [Qemu-arm] " Andrew Jones
2016-04-22 13:26 ` [Qemu-devel] " Andrew Jones
2016-04-23 1:08 ` [Qemu-arm] " Shannon Zhao
2016-04-23 1:08 ` [Qemu-devel] " Shannon Zhao
2016-04-25 10:44 ` [Qemu-arm] " Igor Mammedov
2016-04-25 10:44 ` Igor Mammedov
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=571B2C2D.1070806@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=david.daney@cavium.com \
--cc=drjones@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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.