From: Shannon Zhao <zhaoshenglong@huawei.com>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org,
pbonzini@redhat.com, ganapatrao.kulkarni@caviumnetworks.com,
christoffer.dall@linaro.org, claudio.fontana@huawei.com
Cc: wanghaibin.wang@huawei.com, hangaohuai@huawei.com,
peter.huangpeng@huawei.com, zhaoshenglong@huawei.com
Subject: [Qemu-devel] [RFC PATCH v3 2/3] hw/arm/virt: Don't add memory node in creat_fdt
Date: Tue, 6 Jan 2015 13:57:18 +0800 [thread overview]
Message-ID: <1420523839-11672-3-git-send-email-zhaoshenglong@huawei.com> (raw)
In-Reply-To: <1420523839-11672-1-git-send-email-zhaoshenglong@huawei.com>
To support memory NUMA, don't add memory node in creat_fdt.
But add it in a new function which takes into accout NUMA
topology.
Signed-off-by: Shannon Zhao <zhaoshenglong@huawei.com>
---
hw/arm/virt.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
index fdafa79..505cd29 100644
--- a/hw/arm/virt.c
+++ b/hw/arm/virt.c
@@ -190,8 +190,6 @@ static void create_fdt(VirtBoardInfo *vbi)
* to fill in necessary properties later
*/
qemu_fdt_add_subnode(fdt, "/chosen");
- qemu_fdt_add_subnode(fdt, "/memory");
- qemu_fdt_setprop_string(fdt, "/memory", "device_type", "memory");
/* Clock node, for the benefit of the UART. The kernel device tree
* binding documentation claims the PL011 node clock properties are
--
1.7.1
next prev parent reply other threads:[~2015-01-06 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 5:57 [Qemu-devel] [RFC PATCH v3 0/3] Add support for NUMA on ARM64 Shannon Zhao
2015-01-06 5:57 ` [Qemu-devel] [RFC PATCH v3 1/3] hw/arm/virt: Use memory_region_allocate_system_memory to allocate memory Shannon Zhao
2015-01-06 5:57 ` Shannon Zhao [this message]
2015-01-06 9:55 ` [Qemu-devel] [RFC PATCH v3 2/3] hw/arm/virt: Don't add memory node in creat_fdt Peter Maydell
2015-01-06 10:05 ` Shannon Zhao
2015-01-06 5:57 ` [Qemu-devel] [RFC PATCH v3 3/3] hw/arm/boot: Generate memory dtb according to NUMA topology Shannon Zhao
2015-01-06 9:58 ` Peter Maydell
2015-01-06 10:09 ` Shannon Zhao
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=1420523839-11672-3-git-send-email-zhaoshenglong@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=christoffer.dall@linaro.org \
--cc=claudio.fontana@huawei.com \
--cc=ganapatrao.kulkarni@caviumnetworks.com \
--cc=hangaohuai@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.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).