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 v2 00/11] block: Accept node-name in all node level QMP commands
Date: Wed, 6 Jul 2016 17:20:36 +0200 [thread overview]
Message-ID: <1467818447-2728-1-git-send-email-kwolf@redhat.com> (raw)
As stated in the RFC I sent two weeks ago:
* Node level commands: We need to complete the conversion that makes
commands accept node names instead of BlockBackend names. In some places
we intentionally allow only BlockBackends because we don't know if the
command works in other places than the root. This is okay, but we can
accept node names anyway. We just need to check that the node is a root
node as expected.
This part of the RFC is implemented by this series.
Kevin Wolf (11):
block: Accept node-name for block-stream
block: Accept node-name for block-commit
block: Accept node-name for blockdev-backup
block: Accept node-name for blockdev-mirror
block: Accept node-name for blockdev-snapshot-delete-internal-sync
block: Accept node-name for blockdev-snapshot-internal-sync
block: Accept node-name for change-backing-file
block: Accept node-name for drive-backup
block: Accept node-name for drive-mirror
nbd-server: Use a separate BlockBackend
nbd-server: Allow node name for nbd-server-add
block.c | 2 +
blockdev-nbd.c | 21 +++---
blockdev.c | 196 ++++++++++++++++---------------------------------
include/block/nbd.h | 3 +-
nbd/server.c | 25 +++++--
qapi/block-core.json | 5 +-
qemu-nbd.c | 4 +-
qmp-commands.hx | 2 +-
tests/qemu-iotests/030 | 2 +-
tests/qemu-iotests/041 | 8 +-
tests/qemu-iotests/055 | 7 +-
tests/qemu-iotests/057 | 4 +-
12 files changed, 108 insertions(+), 171 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-07-06 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 15:20 Kevin Wolf [this message]
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 01/11] block: Accept node-name for block-stream Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 02/11] block: Accept node-name for block-commit Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 03/11] block: Accept node-name for blockdev-backup Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 04/11] block: Accept node-name for blockdev-mirror Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 05/11] block: Accept node-name for blockdev-snapshot-delete-internal-sync Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 06/11] block: Accept node-name for blockdev-snapshot-internal-sync Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 07/11] block: Accept node-name for change-backing-file Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 08/11] block: Accept node-name for drive-backup Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 09/11] block: Accept node-name for drive-mirror Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 10/11] nbd-server: Use a separate BlockBackend Kevin Wolf
2016-07-06 15:20 ` [Qemu-devel] [PATCH v2 11/11] nbd-server: Allow node name for nbd-server-add Kevin Wolf
2016-07-06 15:24 ` [Qemu-devel] [RFC PATCH v2 00/11] block: Accept node-name in all node level QMP commands Kevin Wolf
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=1467818447-2728-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).