From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
hutao@cn.fujitsu.com, qemu-stable@nongnu.org,
luonengjun@huawei.com, peter.huangpeng@huawei.com,
qemu-devel@nongnu.org, pbonzini@redhat.com,
gaowanlong@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH 1/2] pc-dimm: No numa option shouldn't break hotplug memory feature
Date: Mon, 22 Sep 2014 14:17:28 +0300 [thread overview]
Message-ID: <20140922111728.GB14882@redhat.com> (raw)
In-Reply-To: <20140919143746.68f082b9@nial.usersys.redhat.com>
On Fri, Sep 19, 2014 at 02:37:46PM +0200, Igor Mammedov wrote:
> On Tue, 16 Sep 2014 18:39:15 +0800
> zhanghailiang <zhang.zhanghailiang@huawei.com> wrote:
>
> > If we do not configure numa option, memory hotplug should work as well.
> > It should not depend on numa option.
> >
> > Steps to reproduce:
> > (1) Start VM: qemu-kvm -m 1024,slots=4,maxmem=8G
> > (2) Hotplug memory
> > It will fail and reports:
> > "'DIMM property node has value 0' which exceeds the number of numa nodes: 0"
> >
> > Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> > ---
> > hw/mem/pc-dimm.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/hw/mem/pc-dimm.c b/hw/mem/pc-dimm.c
> > index 5bfc5b7..a800ea7 100644
> > --- a/hw/mem/pc-dimm.c
> > +++ b/hw/mem/pc-dimm.c
> > @@ -252,7 +252,7 @@ static void pc_dimm_realize(DeviceState *dev, Error **errp)
> > error_setg(errp, "'" PC_DIMM_MEMDEV_PROP "' property is not set");
> > return;
> > }
> > - if (dimm->node >= nb_numa_nodes) {
> > + if ((nb_numa_nodes > 0) && (dimm->node >= nb_numa_nodes)) {
> > error_setg(errp, "'DIMM property " PC_DIMM_NODE_PROP " has value %"
> > PRIu32 "' which exceeds the number of numa nodes: %d",
> > dimm->node, nb_numa_nodes);
>
> Reviewed-By: Igor Mammedov <imammedo@redhat.com>
I read:
> Hmm, I have just tested this, and Yes, it didn't work for Windows guest.
> Thanks for your kind reminder.;)
So should I expect v2 which works with windows?
--
MST
next prev parent reply other threads:[~2014-09-22 11:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 10:39 [Qemu-devel] [PATCH 0/2] fix two bugs about numa _and_ hotplug memory feature zhanghailiang
2014-09-16 10:39 ` [Qemu-devel] [PATCH 1/2] pc-dimm: No numa option shouldn't break " zhanghailiang
2014-09-17 8:32 ` Hu Tao
2014-09-17 9:25 ` zhanghailiang
2014-09-17 10:00 ` Tang Chen
2014-09-17 10:19 ` Andrey Korolyov
2014-09-18 0:58 ` Hu Tao
2014-09-19 12:26 ` Igor Mammedov
2014-09-22 9:03 ` Tang Chen
2014-09-22 9:46 ` zhanghailiang
2014-09-23 8:40 ` Igor Mammedov
2014-09-23 8:58 ` Tang Chen
2014-09-23 10:11 ` zhanghailiang
2014-09-23 10:32 ` Tang Chen
2014-09-23 11:12 ` Igor Mammedov
2014-09-23 12:38 ` zhanghailiang
2014-09-19 12:37 ` Igor Mammedov
2014-09-22 11:17 ` Michael S. Tsirkin [this message]
2014-09-23 9:01 ` Igor Mammedov
2014-09-23 10:07 ` zhanghailiang
2014-09-23 11:13 ` Igor Mammedov
2014-09-16 10:39 ` [Qemu-devel] [PATCH 2/2] numa/pc-dimm: Fix stat of memory size in node when hotplug memory zhanghailiang
2014-09-16 11:20 ` Igor Mammedov
2014-09-17 8:22 ` zhanghailiang
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=20140922111728.GB14882@redhat.com \
--to=mst@redhat.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=luonengjun@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=zhang.zhanghailiang@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).