From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: armbru@redhat.com, mreitz@redhat.com, kwolf@redhat.com,
den@openvz.org, vsementsov@virtuozzo.com, rkagan@virtuozzo.com,
andrey.shinkevich@virtuozzo.com
Subject: [Qemu-devel] [PATCH 0/3] iotests: check whitelisted formats
Date: Mon, 4 Mar 2019 13:08:37 +0300 [thread overview]
Message-ID: <1551694120-768127-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
Some test cases require specific formats to be supported by QEMU. The
list of formats supported by the block layer doesn't take whitelists
into account. This series manages this issue. The method decorator
skip_if_unsupported() checks if requested formats are whitelisted.
The sample output is shown with the sample test #139.
Andrey Shinkevich (3):
block: iterate_format with account of whitelisting
iotests: ask QEMU for supported formats
iotests: check whitelisted formats
block.c | 23 ++++++++++++++++----
blockdev.c | 4 +++-
include/block/block.h | 2 +-
qemu-img.c | 2 +-
tests/qemu-iotests/139 | 2 ++
tests/qemu-iotests/check | 16 +++++++++++++-
tests/qemu-iotests/iotests.py | 50 +++++++++++++++++++++++++++++++++++++++++++
7 files changed, 91 insertions(+), 8 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-03-04 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 10:08 Andrey Shinkevich [this message]
2019-03-04 10:08 ` [Qemu-devel] [PATCH 1/3] block: iterate_format with account of whitelisting Andrey Shinkevich
2019-03-04 10:08 ` [Qemu-devel] [PATCH 2/3] iotests: ask QEMU for supported formats Andrey Shinkevich
2019-03-06 14:31 ` Kevin Wolf
2019-03-06 18:03 ` Andrey Shinkevich
2019-03-06 14:51 ` Kevin Wolf
2019-03-06 17:59 ` Andrey Shinkevich
2019-03-06 18:07 ` Kevin Wolf
2019-03-04 10:08 ` [Qemu-devel] [PATCH 3/3] iotests: check whitelisted formats Andrey Shinkevich
2019-03-06 14:52 ` Kevin Wolf
2019-03-06 17:53 ` Andrey Shinkevich
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=1551694120-768127-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.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 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.