From: "Benoît Canet" <benoit@irqsave.net>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com,
"Benoît Canet" <benoit@irqsave.net>,
jcody@redhat.com, armbru@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [RFC V3 0/7] Giving names to BlockDriverState graph nodes
Date: Tue, 3 Dec 2013 14:25:58 +0100 [thread overview]
Message-ID: <1386077165-19577-1-git-send-email-benoit@irqsave.net> (raw)
This partial series start to add some node-name manipulation from QMP.
In particular it allow to take snapshots of quorum files.
I post it in a partial state to spread the reviewing load.
Best regards
Benoît
Benoît Canet (7):
block: Add bs->node_name to hold the name of a bs node of the bs
graph.
block: Allow the user to define "node-name" option.
qapi: Add skeletton of command to query a drive bs graph.
qmp: Allow block_passwd to manipulate bs graph nodes.
qmp: Allow block_resize to manipulate bs graph nodes.
block: Create authorizations mechanism for external snapshots.
qmp: Allow to take external snapshots on bs graphs node.
block.c | 201 +++++++++++++++++++++++++++++++++++++++-------
block/blkverify.c | 4 +-
block/iscsi.c | 2 +-
block/vmdk.c | 2 +-
block/vvfat.c | 4 +-
blockdev.c | 89 +++++++++++++++-----
hmp.c | 8 +-
hw/block/xen_disk.c | 2 +-
include/block/block.h | 22 +++--
include/block/block_int.h | 18 ++++-
qapi-schema.json | 64 +++++++++++++--
qemu-img.c | 6 +-
qemu-io.c | 2 +-
qemu-nbd.c | 2 +-
qmp-commands.hx | 17 +++-
15 files changed, 363 insertions(+), 80 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-12-03 13:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 13:25 Benoît Canet [this message]
2013-12-03 13:25 ` [Qemu-devel] [RFC V3 1/7] block: Add bs->node_name to hold the name of a bs node of the bs graph Benoît Canet
2013-12-04 23:26 ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 2/7] block: Allow the user to define "node-name" option Benoît Canet
2013-12-04 23:33 ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 3/7] qapi: Add skeletton of command to query a drive bs graph Benoît Canet
2013-12-04 3:10 ` Fam Zheng
2013-12-04 23:46 ` Eric Blake
2013-12-05 14:24 ` Benoît Canet
2013-12-05 14:38 ` Eric Blake
2013-12-05 14:43 ` Benoît Canet
2013-12-05 14:59 ` Eric Blake
2013-12-05 16:37 ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 4/7] qmp: Allow block_passwd to manipulate bs graph nodes Benoît Canet
2013-12-04 23:56 ` Eric Blake
2013-12-05 14:12 ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 5/7] qmp: Allow block_resize " Benoît Canet
2013-12-05 0:01 ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 6/7] block: Create authorizations mechanism for external snapshots Benoît Canet
2013-12-04 3:35 ` Fam Zheng
2013-12-04 5:22 ` Benoît Canet
2013-12-04 3:47 ` Fam Zheng
2013-12-04 5:20 ` Benoît Canet
2013-12-04 6:12 ` Fam Zheng
2013-12-04 6:34 ` Benoît Canet
2013-12-04 7:03 ` Fam Zheng
2013-12-05 14:52 ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 7/7] qmp: Allow to take external snapshots on bs graphs node Benoît Canet
2013-12-04 3:51 ` Fam Zheng
2013-12-04 5:15 ` Benoît Canet
2013-12-05 0:11 ` Eric Blake
2013-12-05 14:16 ` Benoît Canet
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=1386077165-19577-1-git-send-email-benoit@irqsave.net \
--to=benoit@irqsave.net \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@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).