From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Benoît Canet" <benoit@irqsave.net>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Max Reitz" <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] block: Allow JSON filenames
Date: Tue, 6 May 2014 21:30:21 +0200 [thread overview]
Message-ID: <1399404625-6093-1-git-send-email-mreitz@redhat.com> (raw)
This series acts as some kind of alternative or v4 to the "block/json:
Add JSON protocol driver" series. It makes bdrv_open() parse filenames
prefixed by "json:" as JSON objects (discarding the prefix beforehand)
and then use the resulting QDict as the options for the block device to
be opened with a NULL filename.
The purpose of this is that it may sometimes be desirable to specify
options for a block device where only a filename can be given, e.g., for
backing files. Using this should obviously be the exception, but it is
nice to have if actually needed.
After having written this series, I do indeed agree that it is much
nicer than the old version of having a dedicated "virtual" block driver
for this purpose.
Patches 1, 2 and 4 are taken directly from the block/json v3 (see
backport-diff output).
git-backport-diff against [PATCH v3 00/12] block/json:
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/4:[----] [--] 'qdict: Add qdict_join()'
002/4:[----] [--] 'check-qdict: Add test for qdict_join()'
003/4:[down] 'block: Allow JSON filenames'
004/4:[----] [-C] 'iotests: Add test for the JSON protocol'
Max Reitz (4):
qdict: Add qdict_join()
check-qdict: Add test for qdict_join()
block: Allow JSON filenames
iotests: Add test for the JSON protocol
block.c | 41 +++++++++++++++
include/qapi/qmp/qdict.h | 3 ++
qobject/qdict.c | 32 ++++++++++++
tests/check-qdict.c | 87 ++++++++++++++++++++++++++++++++
tests/qemu-iotests/089 | 123 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/089.out | 39 ++++++++++++++
tests/qemu-iotests/group | 1 +
7 files changed, 326 insertions(+)
create mode 100755 tests/qemu-iotests/089
create mode 100644 tests/qemu-iotests/089.out
--
1.9.2
next reply other threads:[~2014-05-06 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 19:30 Max Reitz [this message]
2014-05-06 19:30 ` [Qemu-devel] [PATCH 1/4] qdict: Add qdict_join() Max Reitz
2014-05-06 19:30 ` [Qemu-devel] [PATCH 2/4] check-qdict: Add test for qdict_join() Max Reitz
2014-05-06 19:30 ` [Qemu-devel] [PATCH 3/4] block: Allow JSON filenames Max Reitz
2014-05-06 19:57 ` Eric Blake
2014-05-06 20:00 ` Max Reitz
2014-05-06 20:28 ` Eric Blake
2014-05-06 20:29 ` Max Reitz
2014-05-07 8:39 ` Kevin Wolf
2014-05-08 17:54 ` Max Reitz
2014-05-06 19:30 ` [Qemu-devel] [PATCH 4/4] iotests: Add test for the JSON protocol Max Reitz
2014-05-06 20:04 ` Eric Blake
2014-05-06 20:04 ` 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=1399404625-6093-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=benoit@irqsave.net \
--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).