From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, hreitz@redhat.com, eblake@redhat.com,
kwolf@redhat.com, vsementsov@virtuozzo.com, jsnow@redhat.com,
nikita.lapshin@virtuozzo.com
Subject: [PATCH v2 0/4] block/dirty-bitmaps: fix and improve bitmap merge
Date: Tue, 22 Feb 2022 17:18:29 +0100 [thread overview]
Message-ID: <20220222161833.1453641-1-vsementsov@virtuozzo.com> (raw)
v2:
01: take older patch which is better and has r-b
02: add Nikita's r-b
03: rewrite to keep original logic of no backup on failure path
04: fix comment, add missed "ret = true", keep Nikita's r-b
Vladimir Sementsov-Ogievskiy (4):
block/dirty-bitmap: bdrv_merge_dirty_bitmap(): add return value
block: block_dirty_bitmap_merge(): fix error path
block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap
block: simplify handling of try to merge different sized bitmaps
include/block/block_int.h | 2 +-
include/block/dirty-bitmap.h | 2 +-
include/qemu/hbitmap.h | 15 ++----------
block/backup.c | 6 ++---
block/dirty-bitmap.c | 36 ++++++++++++++---------------
block/monitor/bitmap-qmp-cmds.c | 41 ++++++++++++++++-----------------
util/hbitmap.c | 25 ++++++--------------
7 files changed, 51 insertions(+), 76 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-22 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 16:18 Vladimir Sementsov-Ogievskiy [this message]
2022-02-22 16:18 ` [PATCH v2 1/4] block/dirty-bitmap: bdrv_merge_dirty_bitmap(): add return value Vladimir Sementsov-Ogievskiy
2022-02-22 16:18 ` [PATCH v2 2/4] block: block_dirty_bitmap_merge(): fix error path Vladimir Sementsov-Ogievskiy
2022-02-22 16:18 ` [PATCH v2 3/4] block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap Vladimir Sementsov-Ogievskiy
2022-02-22 16:18 ` [PATCH v2 4/4] block: simplify handling of try to merge different sized bitmaps 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=20220222161833.1453641-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=nikita.lapshin@virtuozzo.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 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.