From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/5] block: Fixes for concurrent block jobs
Date: Mon, 22 Jul 2019 15:33:42 +0200 [thread overview]
Message-ID: <20190722133347.15122-1-mreitz@redhat.com> (raw)
I think the patches speak for themselves now.
(The title of this series alludes to what the iotest added in the final
patch tests.)
v3:
- Rebased on master
- Added two tests to test-bdrv-drain [Kevin]
- Removed new iotest from auto [Thomas]
git-backport-diff against v2:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/5:[----] [--] 'block: Keep subtree drained in drop_intermediate'
002/5:[0004] [FC] 'block: Reduce (un)drains when replacing a child'
003/5:[down] 'tests: Test polling in bdrv_drop_intermediate()'
004/5:[down] 'tests: Test mid-drain bdrv_replace_child_noperm()'
005/5:[0002] [FC] 'iotests: Add test for concurrent stream/commit'
Max Reitz (5):
block: Keep subtree drained in drop_intermediate
block: Reduce (un)drains when replacing a child
tests: Test polling in bdrv_drop_intermediate()
tests: Test mid-drain bdrv_replace_child_noperm()
iotests: Add test for concurrent stream/commit
block.c | 51 ++--
tests/test-bdrv-drain.c | 475 +++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/258 | 163 +++++++++++++
tests/qemu-iotests/258.out | 33 +++
tests/qemu-iotests/group | 1 +
5 files changed, 707 insertions(+), 16 deletions(-)
create mode 100755 tests/qemu-iotests/258
create mode 100644 tests/qemu-iotests/258.out
--
2.21.0
next reply other threads:[~2019-07-22 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 13:33 Max Reitz [this message]
2019-07-22 13:33 ` [Qemu-devel] [PATCH v3 1/5] block: Keep subtree drained in drop_intermediate Max Reitz
2019-07-22 13:33 ` [Qemu-devel] [PATCH v3 2/5] block: Reduce (un)drains when replacing a child Max Reitz
2019-07-22 13:33 ` [Qemu-devel] [PATCH v3 3/5] tests: Test polling in bdrv_drop_intermediate() Max Reitz
2019-07-22 13:33 ` [Qemu-devel] [PATCH v3 4/5] tests: Test mid-drain bdrv_replace_child_noperm() Max Reitz
2019-07-22 13:33 ` [Qemu-devel] [PATCH v3 5/5] iotests: Add test for concurrent stream/commit Max Reitz
2019-08-07 14:05 ` [Qemu-devel] [PATCH v3 0/5] block: Fixes for concurrent block jobs Kevin Wolf
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=20190722133347.15122-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).