From: Wen Congyang <wency@cn.fujitsu.com>
To: Alberto Garcia <berto@igalia.com>,
qemu devel <qemu-devel@nongnu.org>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
qemu block <qemu-block@nongnu.org>,
Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Gonglei <arei.gonglei@huawei.com>,
Yang Hongyang <yanghy@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH v6 4/4] hmp: add monitor command to add/remove a child
Date: Tue, 10 Nov 2015 16:44:34 +0800 [thread overview]
Message-ID: <5641AE72.9020603@cn.fujitsu.com> (raw)
In-Reply-To: <w51y4e7w7d5.fsf@maestria.local.igalia.com>
On 11/09/2015 10:54 PM, Alberto Garcia wrote:
> On Fri 16 Oct 2015 10:57:46 AM CEST, Wen Congyang wrote:
>
>> + .name = "blockdev_change",
>> + .args_type = "op:s,parent:B,child:B?,node:?",
>> + .params = "operation parent [child] [node]",
> [...]
>> + /*
>> + * FIXME: we must specify the parameter child, otherwise,
>> + * we can't specify the parameter node.
>> + */
>> + if (op == CHANGE_OPERATION_ADD) {
>> + has_child = false;
>> + }
>
> So if you want to perform the 'add' operation you must pass both 'child'
> and 'node' but the former will be discarded.
>
> I don't think you really need to do this for the HMP interface, but it's
> anyway one more good reason to merge 'child' and 'node'.
Do you mean there is no need to implement the HMP interface?
Thanks
Wen Congyang
>
> Berto
> .
>
next prev parent reply other threads:[~2015-11-10 8:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 8:57 [Qemu-devel] [PATCH v6 0/4] qapi: child add/delete support Wen Congyang
2015-10-16 8:57 ` [Qemu-devel] [PATCH v6 1/4] Add new block driver interface to add/delete a BDS's child Wen Congyang
2015-10-19 11:10 ` Alberto Garcia
2015-10-16 8:57 ` [Qemu-devel] [PATCH v6 2/4] quorum: implement bdrv_add_child() and bdrv_del_child() Wen Congyang
2015-10-19 12:23 ` Alberto Garcia
2015-10-16 8:57 ` [Qemu-devel] [PATCH v6 3/4] qmp: add monitor command to add/remove a child Wen Congyang
2015-11-05 13:49 ` Alberto Garcia
2015-11-06 0:50 ` Wen Congyang
2015-11-09 14:42 ` Alberto Garcia
2015-11-10 7:23 ` Wen Congyang
2015-11-10 9:24 ` Markus Armbruster
2015-11-09 16:04 ` Kevin Wolf
2015-11-10 1:40 ` Wen Congyang
2015-11-13 10:25 ` Wen Congyang
2015-11-13 10:53 ` Kevin Wolf
2015-11-13 11:19 ` Wen Congyang
2015-11-13 11:42 ` Kevin Wolf
2015-10-16 8:57 ` [Qemu-devel] [PATCH v6 4/4] hmp: " Wen Congyang
2015-11-09 14:54 ` Alberto Garcia
2015-11-10 8:44 ` Wen Congyang [this message]
2015-10-30 6:11 ` [Qemu-devel] [PATCH v6 0/4] qapi: child add/delete support Wen Congyang
2015-11-13 9:28 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-11-13 9:37 ` Wen Congyang
2015-11-13 10:14 ` Stefan Hajnoczi
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=5641AE72.9020603@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=eddie.dong@intel.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=yanghy@cn.fujitsu.com \
--cc=yunhong.jiang@intel.com \
--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).