From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC for-2.7 0/1] block/qapi: Add query-block-node-tree
Date: Tue, 29 Mar 2016 18:09:20 +0200 [thread overview]
Message-ID: <20160329160920.GG4600@noname.redhat.com> (raw)
In-Reply-To: <56FAA5BB.8030801@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
Am 29.03.2016 um 17:56 hat Max Reitz geschrieben:
> On 29.03.2016 17:51, Kevin Wolf wrote:
> > Am 24.03.2016 um 20:07 hat Max Reitz geschrieben:
> >> As I responded to:
> >> - http://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg04464.html
> >> - http://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg05680.html
> >>
> >> I think a general solution for querying the block node tree would be
> >> nice (I don't think we actually have one). The single patch in this
> >> series implements such a command.
> >>
> >> However, this is an RFC because I'm not sure whether we really want this
> >> and thus I didn't want to write the necessary tests for something we may
> >> be going to discard anyway.
> >
> > I think we do want to have a way to query the tree structure in QMP. The
> > part that I'm so sure about is whether we want a recursive command or
> > one that just covers the children of a single node. If we want the
> > latter, just adding a children field (which maps role names to node
> > names) to query-block might be enough.
>
> Sounds fine in principle to me, but I'd like to add that I think we may
> want to have a new command for querying a specific BDS. You don't get
> much choice which nodes you query with query-block, and
> query-named-block-nodes seems a bit bloated to me by now...
Maybe we need to start over with a new query-block-node command that
takes a node name (or BB name as an alias for its root node) and returns
information only about that node. That is, it adds node-name support
compared to query-block, but it removes the recursive crap for backing
files that we added there.
> About the "mapping role names to node names" though; I suppose you mean
> like { "file": "file-node", "backing": "other-qcow2-node" }. I'd have
> loved to do that, but I couldn't imagine a way to represent that in the
> QAPI schema.
Eric and Markus will tell us, but if nothing else helps:
{ 'children': 'any' }
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-03-29 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 19:07 [Qemu-devel] [RFC for-2.7 0/1] block/qapi: Add query-block-node-tree Max Reitz
2016-03-24 19:07 ` [Qemu-devel] [RFC for-2.7 1/1] " Max Reitz
2016-03-25 2:50 ` Wen Congyang
2016-03-26 16:27 ` Max Reitz
2016-03-25 6:54 ` Wen Congyang
2016-03-26 16:33 ` Max Reitz
2016-03-28 15:25 ` Eric Blake
2016-03-29 15:29 ` Max Reitz
2016-03-29 15:39 ` Eric Blake
2016-03-29 15:43 ` Max Reitz
2016-03-29 15:51 ` [Qemu-devel] [RFC for-2.7 0/1] " Kevin Wolf
2016-03-29 15:56 ` Max Reitz
2016-03-29 16:09 ` Kevin Wolf [this message]
2016-03-29 16:10 ` Max Reitz
2016-03-30 12:43 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2016-03-30 14:22 ` Max Reitz
2016-03-31 9:49 ` Stefan Hajnoczi
2016-04-01 15:30 ` Max Reitz
2016-04-04 12:35 ` 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=20160329160920.GG4600@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@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).