From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH 0/7] block: Add driver specific options
Date: Fri, 1 Mar 2013 21:13:34 +0100 [thread overview]
Message-ID: <1362168821-25668-1-git-send-email-kwolf@redhat.com> (raw)
Instead of constantly keeping complaining that we need this big -blockdev
things, let's start attacking individual parts of the project. Here is the
first part, allowing block drivers to provide additional -drive options.
Any options that isn't processed by the block layer is passed to the driver
which can use them. If it doesn't, you get an error message like today. At the
end of this series you can specify:
-drive file=test.qcow2,lazy_refcounts=on
This doesn't include a way to specify options for backing files yet, but
I don't think there's anything blocking such extensions on top.
Kevin Wolf (7):
block: Add options QDict to .bdrv_open()
block: Add options QDict to bdrv_open() prototype
Add qdict_clone_shallow()
block: Add options QDict to bdrv_open_common()
qemu-option: Add qemu_opts_absorb_qdict()
block: Support driver specific options in drive_init()
qcow2: Allow lazy refcounts to be enabled on the command line
block.c | 81 ++++++++++++++++++++++++++++++++++++-----------
block/blkverify.c | 2 +-
block/bochs.c | 2 +-
block/cloop.c | 2 +-
block/cow.c | 2 +-
block/dmg.c | 2 +-
block/parallels.c | 2 +-
block/qcow.c | 2 +-
block/qcow2-cluster.c | 2 +-
block/qcow2.c | 43 +++++++++++++++++++++++--
block/qcow2.h | 1 +
block/qed.c | 4 +--
block/raw.c | 2 +-
block/vdi.c | 2 +-
block/vmdk.c | 4 +--
block/vpc.c | 2 +-
block/vvfat.c | 2 +-
blockdev.c | 53 ++++++++++++++++++++++++++-----
hw/xen_disk.c | 2 +-
include/block/block.h | 4 +--
include/block/block_int.h | 3 +-
include/qapi/qmp/qdict.h | 2 ++
include/qemu/option.h | 1 +
qemu-img.c | 6 ++--
qemu-io.c | 2 +-
qemu-nbd.c | 2 +-
qobject/qdict.c | 22 +++++++++++++
util/qemu-option.c | 34 ++++++++++++++++++++
28 files changed, 233 insertions(+), 55 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-03-01 20:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 20:13 Kevin Wolf [this message]
2013-03-01 20:13 ` [Qemu-devel] [PATCH 1/7] block: Add options QDict to .bdrv_open() Kevin Wolf
2013-03-01 21:15 ` Eric Blake
2013-03-01 20:13 ` [Qemu-devel] [PATCH 2/7] block: Add options QDict to bdrv_open() prototype Kevin Wolf
2013-03-01 21:53 ` Eric Blake
2013-03-01 20:13 ` [Qemu-devel] [PATCH 3/7] Add qdict_clone_shallow() Kevin Wolf
2013-03-01 21:55 ` Eric Blake
2013-03-01 20:13 ` [Qemu-devel] [PATCH 4/7] block: Add options QDict to bdrv_open_common() Kevin Wolf
2013-03-01 22:01 ` Eric Blake
2013-03-04 9:28 ` Stefan Hajnoczi
2013-03-01 20:13 ` [Qemu-devel] [PATCH 5/7] qemu-option: Add qemu_opts_absorb_qdict() Kevin Wolf
2013-03-01 22:14 ` Eric Blake
2013-03-01 20:13 ` [Qemu-devel] [PATCH 6/7] block: Support driver specific options in drive_init() Kevin Wolf
2013-03-01 22:26 ` Eric Blake
2013-03-01 20:13 ` [Qemu-devel] [PATCH 7/7] qcow2: Allow lazy refcounts to be enabled on the command line Kevin Wolf
2013-03-01 22:28 ` Eric Blake
2013-03-04 9:29 ` [Qemu-devel] [PATCH 0/7] block: Add driver specific options Stefan Hajnoczi
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=1362168821-25668-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@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).