From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, vsementsov@virtuozzo.com,
den@virtuozzo.com, armbru@redhat.com, mreitz@redhat.com,
jsnow@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] bitmaps: merge bitmaps from different nodes
Date: Fri, 17 May 2019 18:21:09 +0300 [thread overview]
Message-ID: <20190517152111.206494-1-vsementsov@virtuozzo.com> (raw)
Hi all!
We need to copy bitmaps to new top node on external snapshot, to
not break incremental backup chain.
The only thing to do is to allow block-dirty-bitmap-merge to work
with different nodes, here it is.
v2: use 'alternate' type in qapi for specifying source bitmap
instead of adding new field external-bitmaps [Eric]
Vladimir Sementsov-Ogievskiy (2):
qapi: support external bitmaps in block-dirty-bitmap-merge
iotests: test external snapshot with bitmap copying
qapi/block-core.json | 22 +++++++++++++---
block/dirty-bitmap.c | 9 ++++---
blockdev.c | 50 +++++++++++++++++++++++-------------
tests/qemu-iotests/254 | 52 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/254.out | 52 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/group | 1 +
6 files changed, 163 insertions(+), 23 deletions(-)
create mode 100755 tests/qemu-iotests/254
create mode 100644 tests/qemu-iotests/254.out
--
2.18.0
next reply other threads:[~2019-05-17 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 15:21 Vladimir Sementsov-Ogievskiy [this message]
2019-05-17 15:21 ` [Qemu-devel] [PATCH v2 1/2] qapi: support external bitmaps in block-dirty-bitmap-merge Vladimir Sementsov-Ogievskiy
2019-05-17 22:45 ` John Snow
2019-05-20 15:23 ` Eric Blake
2019-05-17 15:21 ` [Qemu-devel] [PATCH v2 2/2] iotests: test external snapshot with bitmap copying Vladimir Sementsov-Ogievskiy
2019-05-18 1:31 ` John Snow
2019-05-20 7:47 ` Vladimir Sementsov-Ogievskiy
2019-05-20 22:50 ` John Snow
2019-06-05 14:51 ` [Qemu-devel] [Qemu-block] " Max Reitz
2019-06-05 15:08 ` Vladimir Sementsov-Ogievskiy
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=20190517152111.206494-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).