From: John Snow <jsnow@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-trivial@nongnu.org, mjt@tls.msk.ru, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qmp-shell: add documentation
Date: Tue, 07 Jul 2015 12:33:31 -0400 [thread overview]
Message-ID: <559BFF5B.4050405@redhat.com> (raw)
In-Reply-To: <20150702113102.39ab42a5@redhat.com>
On 07/02/2015 11:31 AM, Luiz Capitulino wrote:
> On Wed, 1 Jul 2015 14:25:49 -0400
> John Snow <jsnow@redhat.com> wrote:
>
>> I should probably document the changes that were made.
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>
> Looks good to me, CC'ing maintainer.
>
Whoops, didn't realize Markus took this file over, too. Sorry Luiz.
Markus, would you consider staging this? It's purely a documentation
update for only a dev tool, so it doesn't really matter /when/ it lands
either way, just shoring up some changes I made a while back to the
interpreter here.
tldr: "ping"
>> ---
>> scripts/qmp/qmp-shell | 35 +++++++++++++++++++++++++++++++++++
>> 1 file changed, 35 insertions(+)
>>
>> diff --git a/scripts/qmp/qmp-shell b/scripts/qmp/qmp-shell
>> index 65280d2..fa39bf0 100755
>> --- a/scripts/qmp/qmp-shell
>> +++ b/scripts/qmp/qmp-shell
>> @@ -29,6 +29,41 @@
>> # (QEMU) device_add driver=e1000 id=net1
>> # {u'return': {}}
>> # (QEMU)
>> +#
>> +# key=value pairs also support Python or JSON object literal subset notations,
>> +# without spaces. Dictionaries/objects {} are supported as are arrays [].
>> +#
>> +# example-command arg-name1={'key':'value','obj'={'prop':"value"}}
>> +#
>> +# Both JSON and Python formatting should work, including both styles of
>> +# string literal quotes. Both paradigms of literal values should work,
>> +# including null/true/false for JSON and None/True/False for Python.
>> +#
>> +#
>> +# Transactions have the following multi-line format:
>> +#
>> +# transaction(
>> +# action-name1 [ arg-name1=arg1 ] ... [arg-nameN=argN ]
>> +# ...
>> +# action-nameN [ arg-name1=arg1 ] ... [arg-nameN=argN ]
>> +# )
>> +#
>> +# One line transactions are also supported:
>> +#
>> +# transaction( action-name1 ... )
>> +#
>> +# For example:
>> +#
>> +# (QEMU) transaction(
>> +# TRANS> block-dirty-bitmap-add node=drive0 name=bitmap1
>> +# TRANS> block-dirty-bitmap-clear node=drive0 name=bitmap0
>> +# TRANS> )
>> +# {"return": {}}
>> +# (QEMU)
>> +#
>> +# Use the -v and -p options to activate the verbose and pretty-print options,
>> +# which will echo back the properly formatted JSON-compliant QMP that is being
>> +# sent to QEMU, which is useful for debugging and documentation generation.
>>
>> import qmp
>> import json
>
>
next prev parent reply other threads:[~2015-07-07 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 18:25 [Qemu-devel] [PATCH] qmp-shell: add documentation John Snow
2015-07-02 15:31 ` Luiz Capitulino
2015-07-07 16:33 ` John Snow [this message]
2015-07-23 7:36 ` Markus Armbruster
2015-07-27 3:30 ` John Snow
2015-07-27 21:59 ` Eric Blake
2015-07-30 14:48 ` Luiz Capitulino
2015-08-05 9:49 ` Markus Armbruster
2015-07-28 7:51 ` Kashyap Chamarthy
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=559BFF5B.4050405@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).