From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, eblake@redhat.com,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 0/3] Add -blockdev command line option
Date: Mon, 26 Sep 2016 17:27:53 +0200 [thread overview]
Message-ID: <1474903676-5680-1-git-send-email-kwolf@redhat.com> (raw)
This series adds an option that is directly mapped to the blockdev-add QMP
command. It works more or less like -drive, except that it doesn't create a
BlockBackend (creating just a BDS without a BB is impossible with -drive) and
doesn't support legacy options.
Depends on Dan's "[PATCH v13 0/6] QAPI/QOM work for non-scalar object
properties".
v3:
- Some more documentation improvements [Max]
v2:
- Fix uninitialised use of options variable [Eric]
- Use qapi_free_BlockdevOptions() instead of dealloc visitor [Eric]
- Improved documentation to mention dotted syntax, explain use of
-blockdev with -device, include examples and default values [Eric]
Kevin Wolf (3):
block: Add '-blockdev' command line option
doc: Document generic -blockdev options
doc: Document driver-specific -blockdev options
blockdev.c | 12 +++
include/sysemu/sysemu.h | 1 +
qemu-options.hx | 227 +++++++++++++++++++++++++++++++++++++++++-------
vl.c | 53 +++++++++++
4 files changed, 264 insertions(+), 29 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-09-26 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 15:27 Kevin Wolf [this message]
2016-09-26 15:27 ` [Qemu-devel] [PATCH v3 1/3] block: Add '-blockdev' command line option Kevin Wolf
2016-09-26 15:27 ` [Qemu-devel] [PATCH v3 2/3] doc: Document generic -blockdev options Kevin Wolf
2016-09-26 15:27 ` [Qemu-devel] [PATCH v3 3/3] doc: Document driver-specific " Kevin Wolf
2016-09-27 15:21 ` Eric Blake
2016-09-26 15:40 ` [Qemu-devel] [PATCH v3 0/3] Add -blockdev command line option no-reply
2016-09-26 16:15 ` 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=1474903676-5680-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).