From: Kevin Wolf <kwolf@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: famz@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH V5 0/7] Giving names to BlockDriverState graph nodes
Date: Tue, 21 Jan 2014 16:44:49 +0100 [thread overview]
Message-ID: <20140121154449.GO3307@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20140121153642.GM9834@irqsave.net>
Am 21.01.2014 um 16:36 hat Benoît Canet geschrieben:
> Le Tuesday 21 Jan 2014 à 15:33:09 (+0100), Kevin Wolf a écrit :
> > Am 12.12.2013 um 16:33 hat Benoît Canet geschrieben:
> > > v5:
> > > block empty node names [Kevin]
> > > factorize setting of node-name option [Kevin]
> > > NULL terminate node_name on removal [Kevin]
> > > make query-named-block-nodes return BlockDeviceInfo structure [Eric]
> > > Change some doc in query-named-block-nodes [Eric]
> > > Document the choice of the QMP API for node name [Eric]
> > > Use the same authorization as snapshot on block resize [Kevin]
> > > Rebase the series [Kevin]
> > >
> > > 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.
> > > qmp: Add a command to list the named BlockDriverState nodes.
> > > qmp: Allow to change password on named block driver states.
> > > block: Create authorizations mechanism for external snapshot and
> > > resize.
> > > qmp: Allow block_resize to manipulate bs graph nodes.
> > > qmp: Allow to take external snapshots on bs graphs node.
> >
> > One more general question: Now that we have node names, should
> > bdrv_file_open() use node names rather than device names for references?
> > (Well, no, come to think of it, it's not really a question, but more of
> > a request ;-))
> :)
> I don't understand what you mean: I don't see any reference to device_name in
> bdrv_file_open only one in bdrv_open which is used in a printf.
I'm talking about the function parameter 'const char *reference', which
references an existing block device rather than opening a new one. It
doesn't directly use device_name, but it calls bdrv_find().
Kevin
next prev parent reply other threads:[~2014-01-21 15:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 15:33 [Qemu-devel] [PATCH V5 0/7] Giving names to BlockDriverState graph nodes Benoît Canet
2013-12-12 15:33 ` [Qemu-devel] [PATCH V5 1/7] block: Add bs->node_name to hold the name of a bs node of the bs graph Benoît Canet
2014-01-21 3:10 ` Fam Zheng
2013-12-12 15:33 ` [Qemu-devel] [PATCH V5 2/7] block: Allow the user to define "node-name" option Benoît Canet
2014-01-21 3:15 ` Fam Zheng
2014-01-21 14:12 ` Kevin Wolf
2013-12-12 15:33 ` [Qemu-devel] [PATCH V5 3/7] qmp: Add a command to list the named BlockDriverState nodes Benoît Canet
2014-01-21 3:23 ` Fam Zheng
2013-12-12 15:33 ` [Qemu-devel] [PATCH V5 4/7] qmp: Allow to change password on named block driver states Benoît Canet
2014-01-21 3:27 ` Fam Zheng
2014-01-21 14:17 ` Kevin Wolf
2013-12-12 15:33 ` [Qemu-devel] [PATCH V5 5/7] block: Create authorizations mechanism for external snapshot and resize Benoît Canet
2014-01-21 3:45 ` Fam Zheng
2013-12-12 15:33 ` [Qemu-devel] [PATCH V5 6/7] qmp: Allow block_resize to manipulate bs graph nodes Benoît Canet
2014-01-21 3:46 ` Fam Zheng
2013-12-12 15:34 ` [Qemu-devel] [PATCH V5 7/7] qmp: Allow to take external snapshots on bs graphs node Benoît Canet
2014-01-21 3:54 ` Fam Zheng
2014-01-21 14:28 ` Kevin Wolf
2014-01-22 21:33 ` Benoît Canet
2014-01-23 10:20 ` Kevin Wolf
2014-01-16 17:18 ` [Qemu-devel] [PATCH V5 0/7] Giving names to BlockDriverState graph nodes Benoît Canet
2014-01-21 4:04 ` Fam Zheng
2014-01-21 14:33 ` Kevin Wolf
2014-01-21 15:36 ` Benoît Canet
2014-01-21 15:44 ` Kevin Wolf [this message]
2014-01-22 21:44 ` Benoît Canet
2014-01-23 10:14 ` Kevin Wolf
2014-01-22 22:03 ` 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=20140121154449.GO3307@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=mreitz@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).