From: Alberto Garcia <berto@igalia.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Amos Kong <akong@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/1] Get the list of arguments from a QMP command
Date: Wed, 11 Mar 2015 17:02:28 +0100 [thread overview]
Message-ID: <20150311160228.GA27897@igalia.com> (raw)
In-Reply-To: <874mprq1fs.fsf@blackfin.pond.sub.org>
On Wed, Mar 11, 2015 at 11:21:43AM +0100, Markus Armbruster wrote:
> > I can actually try to implement full introspection support, but I
> > would like to know what API you would like. Something like this?
> >
> > 'query-commands'
> > 'query-enums'
> > 'query-events'
> > 'query-types'
> > 'query-unions'
>
> You propose a separate query-FOO for each kind of thing in the
> schema: command, event, the various types. Not fundamentally
> different to a single query-schema. We can discuss which of the two
> approaches is easier to use.
I don't think it makes much difference in terms of complexity
from the QEMU side. I proposed those because query-commands and
query-events already exist, so adding the missing ones seemed the most
straightforward solution to me.
But if query-schema is more convenient I don't have any problem with
that.
> Here's how I'd try to do that. Treat the schema as a graph, its
> nodes are the definitions of types, commands and events are nodes,
> and a use of a type adds an edge from the node containing the use to
> the type. The external interface is exactly the sub-graph reachable
> QMP command and event nodes.
Makes sense.
Berto
next prev parent reply other threads:[~2015-03-11 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 13:51 [Qemu-devel] [PATCH 0/1] Get the list of arguments from a QMP command Alberto Garcia
2015-02-24 13:51 ` [Qemu-devel] [PATCH 1/1] qmp: Add support for requesting the list of arguments from a command Alberto Garcia
2015-03-06 17:11 ` [Qemu-devel] [PATCH 0/1] Get the list of arguments from a QMP command Eric Blake
2015-03-11 9:18 ` Alberto Garcia
2015-03-11 10:21 ` Markus Armbruster
2015-03-11 10:39 ` Kevin Wolf
2015-03-11 16:02 ` Alberto Garcia [this message]
2015-03-11 19:22 ` Markus Armbruster
2015-03-12 12:39 ` Kevin Wolf
2015-03-14 16:12 ` Markus Armbruster
2015-04-01 15:02 ` Alberto Garcia
2015-04-01 15:30 ` Markus Armbruster
2015-03-11 10:26 ` 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=20150311160228.GA27897@igalia.com \
--to=berto@igalia.com \
--cc=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--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).