From: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
To: Max Reitz <mreitz@redhat.com>, qemu devel <qemu-devel@nongnu.org>,
Eric Blake <eblake@redhat.com>, Alberto Garcia <berto@igalia.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu block <qemu-block@nongnu.org>,
Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Gonglei <arei.gonglei@huawei.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v10 3/3] qmp: add monitor command to add/remove a child
Date: Mon, 7 Mar 2016 17:15:34 +0800 [thread overview]
Message-ID: <56DD46B6.7050702@cn.fujitsu.com> (raw)
In-Reply-To: <56DB267D.9080202@redhat.com>
On 03/06/2016 02:33 AM, Max Reitz wrote:
> On 16.02.2016 10:37, Changlong Xie wrote:
>> From: Wen Congyang <wency@cn.fujitsu.com>
>>
>> The new QMP command name is x-blockdev-change. It's just for adding/removing
>> quorum's child now, and doesn't support all kinds of children, all kinds of
>> operations, nor all block drivers. So it is experimental now.
>>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>> Signed-off-by: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
>> ---
>> blockdev.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> qapi/block-core.json | 32 +++++++++++++++++++++++++++++++
>> qmp-commands.hx | 50 ++++++++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 136 insertions(+)
>>
>> diff --git a/blockdev.c b/blockdev.c
>> index 1f73478..ca040b0 100644
>> --- a/blockdev.c
>> +++ b/blockdev.c
>> @@ -3983,6 +3983,60 @@ out:
>> aio_context_release(aio_context);
>> }
>>
>> +static BlockDriverState *bdrv_find_child(BlockDriverState *parent_bs,
>> + const char *child_name)
>> +{
>> + BdrvChild *child;
>> +
>> + QLIST_FOREACH(child, &parent_bs->children, next) {
>> + if (strcmp(child->name, child_name) == 0) {
>> + return child->bs;
>> + }
>> + }
>> +
>> + return NULL;
>> +}
>
> As I said for patch 1, making this function return a BdrvChild would be
> trivial...
>
Hi Max
okay.
>> +
>> +void qmp_x_blockdev_change(const char *parent, bool has_child,
>> + const char *child, bool has_node,
>> + const char *node, Error **errp)
>> +{
>> + BlockDriverState *parent_bs, *child_bs = NULL, *new_bs = NULL;
>> +
>> + parent_bs = bdrv_lookup_bs(parent, parent, errp);
>> + if (!parent_bs) {
>> + return;
>> + }
>> +
>> + if (has_child == has_node) {
>> + if (has_child) {
>> + error_setg(errp, "The parameters child and node are in conflict");
>> + } else {
>> + error_setg(errp, "Either child or node must be specified");
>> + }
>> + return;
>> + }
>> +
>> + if (has_child) {
>> + child_bs = bdrv_find_child(parent_bs, child);
>> + if (!child_bs) {
>> + error_setg(errp, "Node '%s' does not have child '%s'",
>> + parent, child);
>> + return;
>> + }
>> + bdrv_del_child(parent_bs, child_bs, errp);
>
> ...and then we could pass the BdrvChild here.
ditto
>
> (It's your choice.)
>
>> + }
>> +
>> + if (has_node) {
>> + new_bs = bdrv_find_node(node);
>> + if (!new_bs) {
>> + error_setg(errp, "Node '%s' not found", node);
>> + return;
>> + }
>> + bdrv_add_child(parent_bs, new_bs, errp);
>> + }
>> +}
>> +
>> BlockJobInfoList *qmp_query_block_jobs(Error **errp)
>> {
>> BlockJobInfoList *head = NULL, **p_next = &head;
>> diff --git a/qapi/block-core.json b/qapi/block-core.json
>> index 33012b8..92eb7fe 100644
>> --- a/qapi/block-core.json
>> +++ b/qapi/block-core.json
>> @@ -2482,3 +2482,35 @@
>> ##
>> { 'command': 'block-set-write-threshold',
>> 'data': { 'node-name': 'str', 'write-threshold': 'uint64' } }
>> +
>> +##
>> +# @x-blockdev-change
>> +#
>> +# Dynamically reconfigure the block driver state graph. It can be used
>> +# to add, remove, insert or replace a graph node. Currently only the
>> +# Quorum driver implements this feature to add or remove its child. This
>> +# is useful to fix a broken quorum child.
>> +#
>> +# If @node is specified, it will be inserted under @parent. @child
>> +# may not be specified in this case. If both @parent and @child are
>> +# specified but @node is not, @child will be detached from @parent.
>> +#
>> +# @parent: the id or name of the parent node.
>> +#
>> +# @child: #optional the name of a child under the given parent node.
>> +#
>> +# @node: #optional the name of the node that will be added.
>> +#
>> +# Note: this command is experimental, and its API is not stable. It
>> +# does not support all kinds of operations, all kinds of children, nor
>> +# all block drivers.
>> +#
>> +# Warning: The data in a new quorum child MUST be consistent with that of
>> +# the rest of the array.
>> +#
>> +# Since: 2.6
>> +##
>> +{ 'command': 'x-blockdev-change',
>> + 'data' : { 'parent': 'str',
>> + '*child': 'str',
>> + '*node': 'str' } }
>> diff --git a/qmp-commands.hx b/qmp-commands.hx
>> index 020e5ee..1c9a06f 100644
>> --- a/qmp-commands.hx
>> +++ b/qmp-commands.hx
>> @@ -4364,6 +4364,56 @@ Example:
>> EQMP
>>
>> {
>> + .name = "x-blockdev-change",
>> + .args_type = "parent:B,child:B?,node:B?",
>> + .mhandler.cmd_new = qmp_marshal_x_blockdev_change,
>> + },
>> +
>> +SQMP
>> +x-blockdev-change
>> +-----------------
>> +
>> +Dynamically reconfigure the block driver state graph. It can be used
>> +to add, remove, insert or replace a graph node. Currently only the
>> +Quorum driver implements this feature to add or remove its child. This
>> +is useful to fix a broken quorum child.
>
> The explanation of its behavior is missing here (the second paragraph in
> the qapi/block-core.json comment).
>
Ditto.
Thanks
-Xie
> Max
>
>> +
>> +Arguments:
>> +- "parent": the id or name of the parent node (json-string)
>> +- "child": the name of a child under the given parent node (json-string, optional)
>> +- "node": the name of the node that will be added (json-string, optional)
>> +
>> +Note: this command is experimental, and not a stable API. It doesn't
>> +support all kinds of operations, all kinds of children, nor all block
>> +drivers.
>> +
>> +Warning: The data in a new quorum child MUST be consistent with that of
>> +the rest of the array.
>> +
>> +Example:
>> +
>> +Add a new node to a quorum
>> +-> { "execute": "blockdev-add",
>> + "arguments": { "options": { "driver": "raw",
>> + "node-name": "new_node",
>> + "id": "test_new_node",
>> + "file": { "driver": "file",
>> + "filename": "test.raw" } } } }
>> +<- { "return": {} }
>> +-> { "execute": "x-blockdev-change",
>> + "arguments": { "parent": "disk1",
>> + "node": "new_node" } }
>> +<- { "return": {} }
>> +
>> +Delete a quorum's node
>> +-> { "execute": "x-blockdev-change",
>> + "arguments": { "parent": "disk1",
>> + "child": "children.1" } }
>> +<- { "return": {} }
>> +
>> +EQMP
>> +
>> + {
>> .name = "query-named-block-nodes",
>> .args_type = "",
>> .mhandler.cmd_new = qmp_marshal_query_named_block_nodes,
>>
>
>
prev parent reply other threads:[~2016-03-07 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 9:37 [Qemu-devel] [PATCH v10 0/3] qapi: child add/delete support Changlong Xie
2016-02-16 9:37 ` [Qemu-devel] [PATCH v10 1/3] Add new block driver interface to add/delete a BDS's child Changlong Xie
2016-03-05 17:27 ` Max Reitz
2016-03-07 4:16 ` Changlong Xie
2016-03-07 15:23 ` Max Reitz
2016-02-16 9:37 ` [Qemu-devel] [PATCH v10 2/3] quorum: implement bdrv_add_child() and bdrv_del_child() Changlong Xie
2016-03-05 18:13 ` Max Reitz
2016-03-07 9:13 ` Changlong Xie
2016-03-07 16:02 ` Eric Blake
2016-03-07 16:02 ` Max Reitz
2016-03-08 2:57 ` Changlong Xie
2016-03-09 15:27 ` Max Reitz
2016-03-08 1:42 ` Changlong Xie
2016-02-16 9:37 ` [Qemu-devel] [PATCH v10 3/3] qmp: add monitor command to add/remove a child Changlong Xie
2016-03-05 18:33 ` Max Reitz
2016-03-07 9:15 ` Changlong Xie [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=56DD46B6.7050702@cn.fujitsu.com \
--to=xiecl.fnst@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=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).