From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Max Reitz <mreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Markus Armbruster <armbru@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 7/7] iotests: add iotest 236 for testing bitmap merge
Date: Wed, 12 Dec 2018 20:27:08 -0600 [thread overview]
Message-ID: <9c7b8bbe-6f63-ed65-61c4-dbbae5f07d07@redhat.com> (raw)
In-Reply-To: <20181213015013.15350-8-jsnow@redhat.com>
On 12/12/18 7:50 PM, John Snow wrote:
> New interface, new smoke test.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> tests/qemu-iotests/236 | 123 +++++++++++++++++
> tests/qemu-iotests/236.out | 265 +++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/group | 1 +
> 3 files changed, 389 insertions(+)
> create mode 100755 tests/qemu-iotests/236
> create mode 100644 tests/qemu-iotests/236.out
>
> diff --git a/tests/qemu-iotests/236 b/tests/qemu-iotests/236
> + log('')
> + log('--- Disabling B & Adding C ---\n')
> + vm.qmp_log("transaction", actions=[
> + { "type": "block-dirty-bitmap-disable",
> + "data": { "node": "drive0", "name": "bitmapB" }},
> + { "type": "block-dirty-bitmap-add",
> + "data": { "node": "drive0", "name": "bitmapC" }}
> + ])
Just for grins, what happens if we extend that transaction to
additionally call:
{ "type": "block-dirty-bitmap-disable",
"data": { "node": "drive0", "name": "bitmapC" }},
{ "type": "block-dirty-bitmap-enable",
"data": { "node": "drive0", "name": "bitmapC" }}
Yes, we have a redundancy where plain '-add' coupled with '-disable' in
a transaction does the same as '-add' with 'enabled':false. And I'd
rather keep 'enabled':false as part of '-add', as it's handy to do that
without having to code up a transaction. But the specific act of
toggling the enabled bit twice on a brand new bitmap as part of the same
transaction, while unlikely to be done by libvirt, may still prove to be
a useful validation of our transaction semantics.
> +++ b/tests/qemu-iotests/group
> @@ -233,3 +233,4 @@
> 233 auto quick
> 234 auto quick migration
> 235 auto quick
> +236 auto quick
> \ No newline at end of file
You'll want to fix that.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-12-13 2:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 1:50 [Qemu-devel] [PATCH v2 0/7] bitmaps: remove x- prefix from QMP api John Snow
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 1/7] blockdev: abort transactions in reverse order John Snow
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 2/7] blockdev: n-ary bitmap merge John Snow
2018-12-13 12:25 ` Vladimir Sementsov-Ogievskiy
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 3/7] block: remove 'x' prefix from experimental bitmap APIs John Snow
2018-12-13 12:39 ` Vladimir Sementsov-Ogievskiy
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 4/7] iotests.py: don't abort if IMGKEYSECRET is undefined John Snow
2018-12-13 2:16 ` Eric Blake
2018-12-13 12:42 ` Vladimir Sementsov-Ogievskiy
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 5/7] iotests: add filter_generated_node_ids John Snow
2018-12-13 2:16 ` Eric Blake
2018-12-13 12:45 ` Vladimir Sementsov-Ogievskiy
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 6/7] iotests: allow pretty-print for qmp_log John Snow
2018-12-13 2:20 ` Eric Blake
2018-12-13 18:26 ` John Snow
2018-12-13 13:09 ` Vladimir Sementsov-Ogievskiy
2018-12-14 20:51 ` John Snow
2018-12-17 9:15 ` Vladimir Sementsov-Ogievskiy
2018-12-13 1:50 ` [Qemu-devel] [PATCH v2 7/7] iotests: add iotest 236 for testing bitmap merge John Snow
2018-12-13 2:27 ` Eric Blake [this message]
2018-12-13 18:28 ` John Snow
2018-12-13 13:50 ` Vladimir Sementsov-Ogievskiy
2018-12-13 18:38 ` John Snow
2018-12-13 6:19 ` [Qemu-devel] [PATCH v2 0/7] bitmaps: remove x- prefix from QMP api no-reply
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=9c7b8bbe-6f63-ed65-61c4-dbbae5f07d07@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@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).