From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
vsementsov@virtuozzo.com, Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] qapi: block-dirty-bitmap-remove transaction action
Date: Mon, 15 Jul 2019 15:48:27 -0400 [thread overview]
Message-ID: <bfd251ed-2f86-f463-b682-cd00c1caba51@redhat.com> (raw)
In-Reply-To: <20190708220502.12977-1-jsnow@redhat.com>
On 7/8/19 6:04 PM, John Snow wrote:
> Hi, this is a proposal based off of Vladimir's patchset:
> [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action
>
> ===
> V3:
> ===
>
> 001/3:[----] [--] 'blockdev: reduce aio_context locked sections in bitmap add/remove'
> 002/3:[0024] [FC] 'qapi: implement block-dirty-bitmap-remove transaction action'
> 003/3:[----] [--] 'iotests: test bitmap moving inside 254'
>
> - Changed "squelch_persistence" to "skip_store"
> - Use Max's suggestion for return expr
>
> ===
> V2:
> ===
>
> It replaces patches two and three with a modified patch (now patch 2)
> that foregoes the need for a hide()/unhide() bitmap API. I think it's
> suitable as a smaller alternative, but I'm not sure if it covers all
> of the use cases of the original series.
>
> Patches 1 and 3 (formerly 4) included as-is.
>
> John Snow (1):
> qapi: implement block-dirty-bitmap-remove transaction action
>
> Vladimir Sementsov-Ogievskiy (2):
> blockdev: reduce aio_context locked sections in bitmap add/remove
> iotests: test bitmap moving inside 254
>
> block.c | 2 +-
> block/dirty-bitmap.c | 15 +++--
> blockdev.c | 105 ++++++++++++++++++++++++++-------
> include/block/dirty-bitmap.h | 2 +-
> migration/block-dirty-bitmap.c | 2 +-
> qapi/transaction.json | 2 +
> tests/qemu-iotests/254 | 30 +++++++++-
> tests/qemu-iotests/254.out | 82 +++++++++++++++++++++++++
> 8 files changed, 206 insertions(+), 34 deletions(-)
>
Thanks, applied to my bitmaps tree:
https://github.com/jnsnow/qemu/commits/bitmaps
https://github.com/jnsnow/qemu.git
--js
(Vladimir: if this isn't amenable to you, it's going in for 4.2, so we
have until the next freeze to change it. Let me know, OK?)
next prev parent reply other threads:[~2019-07-15 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 22:04 [Qemu-devel] [PATCH v3 0/3] qapi: block-dirty-bitmap-remove transaction action John Snow
2019-07-08 22:05 ` [Qemu-devel] [PATCH v3 1/3] blockdev: reduce aio_context locked sections in bitmap add/remove John Snow
2019-07-15 11:31 ` Max Reitz
2019-07-08 22:05 ` [Qemu-devel] [PATCH v3 2/3] qapi: implement block-dirty-bitmap-remove transaction action John Snow
2019-07-15 11:40 ` Max Reitz
2019-07-15 18:21 ` John Snow
2019-07-24 13:58 ` Vladimir Sementsov-Ogievskiy
2019-07-24 16:13 ` John Snow
2019-07-08 22:05 ` [Qemu-devel] [PATCH v3 3/3] iotests: test bitmap moving inside 254 John Snow
2019-07-15 11:44 ` Max Reitz
2019-07-15 19:48 ` John Snow [this message]
2019-07-24 11:12 ` [Qemu-devel] [PATCH v3 0/3] qapi: block-dirty-bitmap-remove transaction action Vladimir Sementsov-Ogievskiy
2019-07-24 12:52 ` John Snow
2019-07-26 17:26 ` 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=bfd251ed-2f86-f463-b682-cd00c1caba51@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--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).