qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com,
	mreitz@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v3 0/4] transaction support for bitmap merge
Date: Fri, 14 Sep 2018 13:15:44 -0400	[thread overview]
Message-ID: <a9ca19ec-826a-e8c0-0fe5-7e46c084c4c6@redhat.com> (raw)
In-Reply-To: <20180914151515.21242-1-vsementsov@virtuozzo.com>



On 09/14/2018 11:15 AM, Vladimir Sementsov-Ogievskiy wrote:
> This is a last brick, necessary to play with nbd bitmap export in
> conjunction with image fleecing.
> 
> v3:
> 01: fix type in commit message, add John's r-b
> 02: splitted refactoring
> 03: improve commit message, split some refactoring to 02
> 04: add John's r-b
> 05: drop extra state variable, make it local instead. John's r-b.
> 
> 
> v2: don't compare with v1, it is changed a lot, to do the whole thing
>     in .prepare instead of .commit. It is needed to be compatible with
>     backup block job transaction actions [John]
> 
> Vladimir Sementsov-Ogievskiy (5):
>   dirty-bitmap: switch assert-fails to errors in bdrv_merge_dirty_bitmap
>   dirty-bitmap: rename bdrv_undo_clear_dirty_bitmap
>   dirty-bitmap: make it possible to restore bitmap after merge
>   blockdev: rename block-dirty-bitmap-clear transaction handlers
>   qapi: add transaction support for x-block-dirty-bitmap-merge
> 
>  qapi/transaction.json        |  2 ++
>  include/block/block_int.h    |  2 +-
>  include/block/dirty-bitmap.h |  2 +-
>  include/qemu/hbitmap.h       | 25 +++++++++------
>  block/dirty-bitmap.c         | 36 +++++++++++++++++-----
>  blockdev.c                   | 59 +++++++++++++++++++++++++-----------
>  util/hbitmap.c               | 11 +++++--
>  7 files changed, 99 insertions(+), 38 deletions(-)
> 

Reviewed-by: John Snow <jsnow@redhat.com>

  parent reply	other threads:[~2018-09-14 17:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 15:15 [Qemu-devel] [PATCH v3 0/4] transaction support for bitmap merge Vladimir Sementsov-Ogievskiy
2018-09-14 15:15 ` [Qemu-devel] [PATCH v3 1/5] dirty-bitmap: switch assert-fails to errors in bdrv_merge_dirty_bitmap Vladimir Sementsov-Ogievskiy
2018-09-14 15:15 ` [Qemu-devel] [PATCH v3 2/5] dirty-bitmap: rename bdrv_undo_clear_dirty_bitmap Vladimir Sementsov-Ogievskiy
2018-09-14 15:15 ` [Qemu-devel] [PATCH v3 3/5] dirty-bitmap: make it possible to restore bitmap after merge Vladimir Sementsov-Ogievskiy
2018-09-14 15:15 ` [Qemu-devel] [PATCH v3 4/5] blockdev: rename block-dirty-bitmap-clear transaction handlers Vladimir Sementsov-Ogievskiy
2018-09-14 15:15 ` [Qemu-devel] [PATCH v3 5/5] qapi: add transaction support for x-block-dirty-bitmap-merge Vladimir Sementsov-Ogievskiy
2018-09-14 17:15 ` John Snow [this message]
2018-09-14 17:36 ` [Qemu-devel] [PATCH v3 0/4] transaction support for bitmap merge 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=a9ca19ec-826a-e8c0-0fe5-7e46c084c4c6@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@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).