From: Wen Congyang <wency@cn.fujitsu.com>
To: 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: Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
Markus Armbruster <armbru@redhat.com>,
qemu block <qemu-block@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [Patch v8 0/3] qapi: child add/delete support
Date: Thu, 10 Dec 2015 14:10:22 +0800 [thread overview]
Message-ID: <5669174E.3010609@cn.fujitsu.com> (raw)
In-Reply-To: <1448604397-14975-1-git-send-email-wency@cn.fujitsu.com>
Kevin: ping
On 11/27/2015 02:06 PM, Wen Congyang wrote:
> If quorum's child is broken, we can use mirror job to replace it.
> But sometimes, the user only need to remove the broken child, and
> add it later when the problem is fixed.
>
> It is based on the Kevin's child name related patch:
> http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg04949.html
>
> ChangLog:
> v8:
> 1. Rebase to the newest codes
> 2. Address the comments from Eric Blake
> v7:
> 1. Remove the qmp command x-blockdev-change's parameter operation according
> to Kevin's comments.
> 2. Remove the hmp command.
> v6:
> 1. Use a single qmp command x-blockdev-change to replace x-blockdev-child-add
> and x-blockdev-child-delete
> v5:
> 1. Address Eric Blake's comments
> v4:
> 1. drop nbd driver's implementation. We can use human-monitor-command
> to do it.
> 2. Rename the command name.
> v3:
> 1. Don't open BDS in bdrv_add_child(). Use the existing BDS which is
> created by the QMP command blockdev-add.
> 2. The driver NBD can support filename, path, host:port now.
> v2:
> 1. Use bdrv_get_device_or_node_name() instead of new function
> bdrv_get_id_or_node_name()
> 2. Update the error message
> 3. Update the documents in block-core.json
>
> Wen Congyang (3):
> Add new block driver interface to add/delete a BDS's child
> quorum: implement bdrv_add_child() and bdrv_del_child()
> qmp: add monitor command to add/remove a child
>
> block.c | 58 ++++++++++++++++++++--
> block/quorum.c | 124 +++++++++++++++++++++++++++++++++++++++++++++-
> blockdev.c | 54 ++++++++++++++++++++
> include/block/block.h | 9 ++++
> include/block/block_int.h | 5 ++
> qapi/block-core.json | 23 +++++++++
> qmp-commands.hx | 47 ++++++++++++++++++
> 7 files changed, 314 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2015-12-10 6:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 6:06 [Qemu-devel] [Patch v8 0/3] qapi: child add/delete support Wen Congyang
2015-11-27 6:06 ` [Qemu-devel] [Patch v8 1/3] Add new block driver interface to add/delete a BDS's child Wen Congyang
2015-11-27 6:06 ` [Qemu-devel] [Patch v8 2/3] quorum: implement bdrv_add_child() and bdrv_del_child() Wen Congyang
2015-12-15 1:18 ` Li Zhijian
2015-11-27 6:06 ` [Qemu-devel] [Patch v8 3/3] qmp: add monitor command to add/remove a child Wen Congyang
2015-12-15 1:25 ` Li Zhijian
2015-12-10 6:10 ` Wen Congyang [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=5669174E.3010609@cn.fujitsu.com \
--to=wency@cn.fujitsu.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=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=yunhong.jiang@intel.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 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.