From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: armbru@redhat.com, pbonzini@redhat.com, mreitz@redhat.com,
kwolf@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v5 5/6] qapi: new qmp command nbd-server-add-bitmap
Date: Wed, 20 Jun 2018 06:26:52 -0500 [thread overview]
Message-ID: <45f6544a-d384-f3cc-5fd4-c3d5f0268f25@redhat.com> (raw)
In-Reply-To: <20180609151758.17343-6-vsementsov@virtuozzo.com>
On 06/09/2018 10:17 AM, Vladimir Sementsov-Ogievskiy wrote:
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> qapi/block.json | 23 +++++++++++++++++++++++
> blockdev-nbd.c | 23 +++++++++++++++++++++++
> 2 files changed, 46 insertions(+)
I'm tempted to temporarily name this x-nbd-server-add-bitmap, until I
have the counterpart Libvirt patches tested, just in case testing turns
up any tweaks we need to the interface.
>
> diff --git a/qapi/block.json b/qapi/block.json
> index c694524002..ddbca2e286 100644
> --- a/qapi/block.json
> +++ b/qapi/block.json
> @@ -269,6 +269,29 @@
> 'data': {'name': 'str', '*mode': 'NbdServerRemoveMode'} }
>
> ##
> +# @nbd-server-add-bitmap:
> +#
> +# Expose a dirty bitmap associated with the selected export. The bitmap search
> +# starts at the device attached to the export, and includes all backing files.
> +# The exported bitmap is then locked until the NBD export is removed.
The fact that you search the backing chain is at least consistent with
your code.
> +#
> +# @name: Export name.
> +#
> +# @bitmap: Bitmap name to search for.
> +#
> +# @bitmap-export-name: How the bitmap will be seen by nbd clients
> +# (default @bitmap)
Do we really need the flexibility of naming the bitmap differently to
the NBD client than we do in qemu?
> +#
> +# Note: the client must use NBD_OPT_SET_META_CONTEXT with a query of
> +# "qemu:dirty-bitmap:NAME" (where NAME matches @bitmap-export-name) to access
> +# the exposed bitmap.
> +#
> +# Since: 3.0
> +##
> + { 'command': 'nbd-server-add-bitmap',
> + 'data': {'name': 'str', 'bitmap': 'str', '*bitmap-export-name': 'str'} }
> +
> +##
> # @nbd-server-stop:
> #
> # Stop QEMU's embedded NBD server, and unregister all devices previously
> diff --git a/blockdev-nbd.c b/blockdev-nbd.c
> index 65a84739ed..6b0c50732c 100644
> --- a/blockdev-nbd.c
> +++ b/blockdev-nbd.c
> @@ -220,3 +220,26 @@ void qmp_nbd_server_stop(Error **errp)
> nbd_server_free(nbd_server);
> nbd_server = NULL;
> }
> +
> +void qmp_nbd_server_add_bitmap(const char *name, const char *bitmap,
> + bool has_bitmap_export_name,
> + const char *bitmap_export_name,
> + Error **errp)
> +{
> + NBDExport *exp;
> +
> + if (!nbd_server) {
> + error_setg(errp, "NBD server not running");
> + return;
> + }
> +
> + exp = nbd_export_find(name);
> + if (exp == NULL) {
> + error_setg(errp, "Export '%s' is not found", name);
> + return;
> + }
> +
> + nbd_export_bitmap(exp, bitmap,
> + has_bitmap_export_name ? bitmap_export_name : bitmap,
> + errp);
> +}
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-06-20 11:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 15:17 [Qemu-devel] [PATCH v5 0/6] NBD export bitmaps Vladimir Sementsov-Ogievskiy
2018-06-09 15:17 ` [Qemu-devel] [PATCH v5 1/6] nbd/server: fix trace Vladimir Sementsov-Ogievskiy
2018-06-19 18:39 ` Eric Blake
2018-06-09 15:17 ` [Qemu-devel] [PATCH v5 2/6] nbd/server: refactor NBDExportMetaContexts Vladimir Sementsov-Ogievskiy
2018-06-19 19:03 ` Eric Blake
2018-06-09 15:17 ` [Qemu-devel] [PATCH v5 3/6] nbd/server: add nbd_meta_empty_or_pattern helper Vladimir Sementsov-Ogievskiy
2018-06-19 20:24 ` Eric Blake
2018-06-20 9:43 ` Vladimir Sementsov-Ogievskiy
2018-06-09 15:17 ` [Qemu-devel] [PATCH v5 4/6] nbd/server: implement dirty bitmap export Vladimir Sementsov-Ogievskiy
2018-06-20 11:24 ` Eric Blake
2018-06-20 14:04 ` Vladimir Sementsov-Ogievskiy
2018-06-20 15:43 ` Eric Blake
2018-06-20 15:58 ` Eric Blake
2018-06-20 16:27 ` Eric Blake
2018-06-20 17:04 ` Vladimir Sementsov-Ogievskiy
2018-06-20 18:09 ` Eric Blake
2018-06-21 10:09 ` Vladimir Sementsov-Ogievskiy
2018-09-14 16:22 ` Vladimir Sementsov-Ogievskiy
2018-11-29 4:34 ` Eric Blake
2019-01-09 19:21 ` Eric Blake
2019-01-10 7:15 ` Eric Blake
2019-01-17 21:09 ` John Snow
2018-06-09 15:17 ` [Qemu-devel] [PATCH v5 5/6] qapi: new qmp command nbd-server-add-bitmap Vladimir Sementsov-Ogievskiy
2018-06-20 11:26 ` Eric Blake [this message]
2018-06-20 14:13 ` Vladimir Sementsov-Ogievskiy
2018-06-20 18:14 ` Eric Blake
2018-06-21 10:10 ` Vladimir Sementsov-Ogievskiy
2018-06-21 10:23 ` Nikolay Shirokovskiy
2018-06-09 15:17 ` [Qemu-devel] [PATCH v5 6/6] docs/interop: add nbd.txt Vladimir Sementsov-Ogievskiy
2018-06-20 11:33 ` Eric Blake
2018-06-20 14:16 ` Vladimir Sementsov-Ogievskiy
2018-06-20 20:58 ` [Qemu-devel] [Qemu-block] " John Snow
2018-06-21 15:59 ` Vladimir Sementsov-Ogievskiy
2018-06-21 22:10 ` [Qemu-devel] Incremental Backup Status (Was: Re: [Qemu-block] [PATCH v5 6/6] docs/interop: add nbd.txt) John Snow
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=45f6544a-d384-f3cc-5fd4-c3d5f0268f25@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).