From: Amos Kong <akong@redhat.com>
To: Osier Yang <jyang@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4] monitor: introduce query-command-line-options
Date: Thu, 25 Apr 2013 17:50:50 +0800 [thread overview]
Message-ID: <20130425095050.GA2318@t430s.nay.redhat.com> (raw)
In-Reply-To: <5178C1A0.5090804@redhat.com>
On Thu, Apr 25, 2013 at 01:39:44PM +0800, Osier Yang wrote:
> On 25/04/13 13:06, Amos Kong wrote:
> >Libvirt has no way to probe if an option or property is supported,
> >This patch introdues a new qmp command to query command line
> >option information. hmp command isn't added because it's not needed.
> >
> >Signed-off-by: Amos Kong <akong@redhat.com>
> >CC: Osier Yang <jyang@redhat.com>
> >CC: Anthony Liguori <aliguori@us.ibm.com>
> >---
> >V3: fix jaso schema and comments (Eric)
>
> s/jaso/json/,
>
> >V4: fix descriptions, rename command, check enum type, cleanup
> >---
> > qapi-schema.json | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> > qmp-commands.hx | 48 ++++++++++++++++++++++++++++++++++++++
> > util/qemu-config.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 182 insertions(+)
...
> >+{'command': 'query-command-line-options', 'data': { '*option': 'str' },
> >+ 'returns': ['CommandLineOptionInfo']}
> >diff --git a/qmp-commands.hx b/qmp-commands.hx
> >index 4d65422..77fe443 100644
> >--- a/qmp-commands.hx
> >+++ b/qmp-commands.hx
> >@@ -2416,6 +2416,54 @@ EQMP
> > },
> > SQMP
> >+query-command-line-options
> >+--------------------------
> >+
> >+Show command line option schema.
> >+
> >+Return a jaso-array of command line option schema for all options (or for
>
> s/jaso-array/json-array/,
>
> >+the given option), returning an error if the given option doesn't exist.
> >+
> >+Each array entry contains the following:
> >+
> >+- "option": option name (json-string)
> >+- "parameters": an array of json-objects, each describing one
> >+ parameter of the option:
>
> To be consistent, s/an array of json-objects/a json-array/,
>
> How about:
>
> a json-array describes parameters of the option
I will change it to:
"parameters": a json-array describes all parameters of the option:
>
> >+ - "name": parameter name (json-string)
> >+ - "type": parameter type (one of 'string', boolean', 'number',
> >+ or 'size')
> >+ - "help": human readable description of the parameter
> >+ (json-string, optional)
> >+
> >+
--
Amos.
prev parent reply other threads:[~2013-04-25 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 5:06 [Qemu-devel] [PATCH v4] monitor: introduce query-command-line-options Amos Kong
2013-04-25 5:39 ` Osier Yang
2013-04-25 9:50 ` Amos Kong [this message]
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=20130425095050.GA2318@t430s.nay.redhat.com \
--to=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jyang@redhat.com \
--cc=lcapitulino@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 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).