qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com,
	vsementsov@parallels.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v12 05/17] qmp: Add block-dirty-bitmap-enable and block-dirty-bitmap-disable
Date: Wed, 11 Feb 2015 11:26:40 -0500	[thread overview]
Message-ID: <54DB82C0.10104@redhat.com> (raw)
In-Reply-To: <1423532117-14490-6-git-send-email-jsnow@redhat.com>

On 2015-02-09 at 20:35, John Snow wrote:
> This allows to put the dirty bitmap into a disabled state where it is
> read only. A disabled bitmap will ignore any attempts to set or reset
> any of its bits, but can otherwise be renamed, deleted, or re-enabled.
>
> It will be used before backup or writing to persistent file.
>
> Signed-off-by: Fam Zheng<famz@redhat.com>
> Signed-off-by: John Snow<jsnow@redhat.com>
> ---
>   block.c               | 25 +++++++++++++++++++++++++
>   blockdev.c            | 40 ++++++++++++++++++++++++++++++++++++++++
>   include/block/block.h |  3 +++
>   qapi/block-core.json  | 28 ++++++++++++++++++++++++++++
>   qmp-commands.hx       | 10 ++++++++++
>   5 files changed, 106 insertions(+)
>
> diff --git a/block.c b/block.c
> index 83f411f..8d63375 100644
> --- a/block.c
> +++ b/block.c
> @@ -54,6 +54,7 @@
>   struct BdrvDirtyBitmap {
>       HBitmap *bitmap;
>       char *name;
> +    bool disabled;
>       QLIST_ENTRY(BdrvDirtyBitmap) list;
>   };
>   
> @@ -5412,10 +5413,16 @@ BdrvDirtyBitmap *bdrv_create_dirty_bitmap(BlockDriverState *bs,
>       bitmap = g_new0(BdrvDirtyBitmap, 1);
>       bitmap->bitmap = hbitmap_alloc(bitmap_size, ffs(sector_granularity) - 1);
>       bitmap->name = g_strdup(name);
> +    bitmap->disabled = false;

Unnecessary thanks to the g_new0(), but won't hurt.

Reviewed-by: Max Reitz <mreitz@redhat.com>

  reply	other threads:[~2015-02-11 16:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10  1:35 [Qemu-devel] [PATCH v12 00/17] block: incremental backup series John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 01/17] qapi: Add optional field "name" to block dirty bitmap John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 02/17] qmp: Add block-dirty-bitmap-add and block-dirty-bitmap-remove John Snow
2015-02-10 21:56   ` Max Reitz
2015-02-13 22:24   ` Eric Blake
2015-02-13 22:39     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 03/17] block: Introduce bdrv_dirty_bitmap_granularity() John Snow
2015-02-10 22:03   ` Max Reitz
2015-02-11 18:57     ` John Snow
2015-02-11 18:58       ` Max Reitz
2015-02-10 22:13   ` Max Reitz
2015-02-10 22:15     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 04/17] hbitmap: add hbitmap_merge John Snow
2015-02-10 22:16   ` Max Reitz
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 05/17] qmp: Add block-dirty-bitmap-enable and block-dirty-bitmap-disable John Snow
2015-02-11 16:26   ` Max Reitz [this message]
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 06/17] block: Add bitmap successors John Snow
2015-02-11 16:50   ` Max Reitz
2015-02-11 16:51     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 07/17] qmp: Add support of "dirty-bitmap" sync mode for drive-backup John Snow
2015-02-11 17:47   ` Max Reitz
2015-02-11 17:54     ` John Snow
2015-02-11 18:18       ` Max Reitz
2015-02-11 18:31         ` John Snow
2015-02-11 18:33           ` Max Reitz
2015-02-11 21:13     ` John Snow
2015-02-13 17:33   ` Vladimir Sementsov-Ogievskiy
2015-02-13 18:35     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 08/17] qmp: add block-dirty-bitmap-clear John Snow
2015-02-11 18:28   ` Max Reitz
2015-02-11 18:36     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 09/17] qapi: Add transaction support to block-dirty-bitmap operations John Snow
2015-02-11 19:07   ` Max Reitz
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 10/17] qmp: Add dirty bitmap status fields in query-block John Snow
2015-02-11 19:10   ` Max Reitz
2015-02-11 19:19     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 11/17] block: add BdrvDirtyBitmap documentation John Snow
2015-02-11 19:14   ` Max Reitz
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 12/17] block: Ensure consistent bitmap function prototypes John Snow
2015-02-11 19:20   ` Max Reitz
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 13/17] iotests: add invalid input incremental backup tests John Snow
2015-02-11 20:45   ` Max Reitz
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 14/17] iotests: add simple incremental backup case John Snow
2015-02-11 21:40   ` Max Reitz
2015-02-11 22:02     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 15/17] iotests: add transactional incremental backup test John Snow
2015-02-11 21:49   ` Max Reitz
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 16/17] blkdebug: fix "once" rule John Snow
2015-02-11 21:50   ` Max Reitz
2015-02-11 22:04     ` John Snow
2015-02-10  1:35 ` [Qemu-devel] [PATCH v12 17/17] iotests: add incremental backup failure recovery test John Snow
2015-02-11 22:01   ` Max Reitz
2015-02-11 22:08     ` John Snow
2015-02-11 22:11       ` Max Reitz
2015-02-10 16:32 ` [Qemu-devel] [PATCH v12 00/17] block: incremental backup series 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=54DB82C0.10104@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@parallels.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).