From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] block: driver should override flags in bdrv_open()
Date: Mon, 2 Feb 2015 12:08:04 -0500 [thread overview]
Message-ID: <1422896886-12878-1-git-send-email-mreitz@redhat.com> (raw)
BDRV_O_PROTOCOL is an internal qemu flag which a user should be able to
override by explicitly specifying a block driver. This series implements
this and adds two iotests (one for NBD, one for file) to test it.
For the NBD test to succeed, this series relies on
"iotests: Specify format for qemu-nbd".
Also, the second patch's "group" file modifying hunk relies on
"qemu-iotests: add 116 invalid QED input file tests".
Max Reitz (2):
block: driver should override flags in bdrv_open()
iotests: Add tests for overriding BDRV_O_PROTOCOL
block.c | 49 +++++++++++++++++++++-------------
tests/qemu-iotests/051 | 1 -
tests/qemu-iotests/051.out | 3 ---
tests/qemu-iotests/119 | 60 ++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/119.out | 11 ++++++++
tests/qemu-iotests/120 | 65 ++++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/120.out | 15 +++++++++++
tests/qemu-iotests/group | 2 ++
8 files changed, 184 insertions(+), 22 deletions(-)
create mode 100755 tests/qemu-iotests/119
create mode 100644 tests/qemu-iotests/119.out
create mode 100755 tests/qemu-iotests/120
create mode 100644 tests/qemu-iotests/120.out
--
2.1.0
next reply other threads:[~2015-02-02 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 17:08 Max Reitz [this message]
2015-02-02 17:08 ` [Qemu-devel] [PATCH 1/2] block: driver should override flags in bdrv_open() Max Reitz
2015-02-02 17:08 ` [Qemu-devel] [PATCH 2/2] iotests: Add tests for overriding BDRV_O_PROTOCOL Max Reitz
2015-02-27 22:28 ` [Qemu-devel] [PATCH 0/2] block: driver should override flags in bdrv_open() Max Reitz
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=1422896886-12878-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).