From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: aliguori@us.ibm.com, mdroth@linux.vnet.ibm.com,
qemu-devel@nongnu.org, jyang@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>, Amos Kong <akong@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: introduce query-config-schema
Date: Tue, 23 Apr 2013 09:20:40 -0400 [thread overview]
Message-ID: <20130423092040.7179f3ce@redhat.com> (raw)
In-Reply-To: <51755075.1000008@redhat.com>
On Mon, 22 Apr 2013 09:00:05 -0600
Eric Blake <eblake@redhat.com> wrote:
> At any rate, we really DO want introspection, and having it in 1.5 is a
> worthwhile goal. Even if the introspection turns up empty on legacy
> options, having it for the sake of new options is worth the effort.
Agreed. But as you said in another email, we need a JSON representation
for this command. Dumping all options as strings is just like using -help.
Something else that has occurred to me is that, do we want this to be
a QMP command or do we want this to be a command-line option? If we do this
as a QMP command then libvirt would have to actually start QEMU just to
query supported options.
Another interesting point is about full schema introspection. This patch
only supports command-line options. It would be desirable to be able to
introspect all QAPI types and QMP commands, although I'm aware that this
might be a lot of work to do for 1.5.
next prev parent reply other threads:[~2013-04-23 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 9:52 [Qemu-devel] [PATCH] monitor: introduce query-config-schema Amos Kong
2013-04-19 12:02 ` Osier Yang
2013-04-19 12:22 ` Eric Blake
2013-04-19 13:44 ` Osier Yang
2013-04-19 12:39 ` Eric Blake
2013-04-19 13:50 ` Osier Yang
2013-04-19 15:21 ` Paolo Bonzini
2013-04-22 11:48 ` Amos Kong
2013-04-22 12:07 ` Paolo Bonzini
2013-04-22 15:00 ` Eric Blake
2013-04-22 15:16 ` Paolo Bonzini
2013-04-23 2:40 ` Amos Kong
2013-04-23 13:20 ` Luiz Capitulino [this message]
2013-04-23 15:32 ` Eric Blake
2013-04-23 16:55 ` Luiz Capitulino
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=20130423092040.7179f3ce@redhat.com \
--to=lcapitulino@redhat.com \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=jyang@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.