From: Eric Blake <eblake@redhat.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>, qemu-devel@nongnu.org
Cc: "Emilio G. Cota" <cota@braap.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 11/13] instrument: [qapi] Add library loader
Date: Mon, 24 Jul 2017 13:03:46 -0500 [thread overview]
Message-ID: <109e1849-1bf6-5875-b304-7cacbf45f068@redhat.com> (raw)
In-Reply-To: <150091841019.30739.3661641061220051037.stgit@frigg.lan>
[-- Attachment #1: Type: text/plain, Size: 3786 bytes --]
On 07/24/2017 12:46 PM, Lluís Vilanova wrote:
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> ---
> instrument/Makefile.objs | 1 +
> instrument/qmp.c | 71 ++++++++++++++++++++++++++++++++++++
> qapi-schema.json | 3 ++
> qapi/instrument.json | 92 ++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 167 insertions(+)
> create mode 100644 instrument/qmp.c
> create mode 100644 qapi/instrument.json
Adding new files; but I don't see a patch to MAINTAINERS to cover
instrument/*.
> +++ b/qapi/instrument.json
> @@ -0,0 +1,92 @@
> +# *-*- Mode: Python -*-*
> +#
> +# QAPI trace instrumentation control commands.
> +#
> +# Copyright (C) 2012-2017 Lluís Vilanova <vilanova@ac.upc.edu>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or later.
> +# See the COPYING file in the top-level directory.
> +
> +##
> +# @InstrLoadCode:
> +#
> +# Result code of an 'instr-load' command.
> +#
> +# @ok: Correctly loaded.
> +# @unavailable: Service not available.
> +# @error: Error with libdl (see 'msg').
> +#
> +# Since: 2.10
This is a new feature, and you've missed soft freeze. You'll want to
use 2.11 throughout the file.
> +##
> +{ 'enum': 'InstrLoadCode',
> + 'data': [ 'ok', 'unavailable', 'error' ] }
> +
> +##
> +# @InstrLoadResult:
> +#
> +# Result of an 'instr-load' command.
> +#
> +# @code: Result code.
> +# @msg: Additional error message.
Worth a comment that the message is for human consumption, and should
not be further parsed by machine?
Should msg be optional, present only when there is an error?
> +# @handle: Instrumentation library identifier (undefined in case of error).
Should it be an optional member, omitted when there is an error?
> +#
> +# Since: 2.10
> +##
> +{ 'struct': 'InstrLoadResult',
> + 'data': { 'code': 'InstrLoadCode', 'msg': 'str', 'handle': 'int' } }
> +
> +##
> +# @instr-load:
> +#
> +# Load an instrumentation library.
> +#
> +# @path: path to the dynamic instrumentation library
> +# @args: arguments to the dynamic instrumentation library
> +#
> +# Since: 2.10
> +##
> +{ 'command': 'instr-load',
> + 'data': { 'path': 'str', '*args': ['String'] },
Why are you double-nesting things? It's a lot nicer to use ['str']
(that is, your way requires
"arguments":{"path":"/some/path",
"args": [ { "str": "string1" }, { "str": "string2" } ] }
whereas mine only needs:
"arguments":{"path":"/some/path", "args":[ "string1", "string2" ]}
> + 'returns': 'InstrLoadResult' }
> +
> +
> +##
> +# @InstrUnloadCode:
> +#
> +# Result code of an 'instr-unload' command.
> +#
> +# @ok: Correctly unloaded.
> +# @unavailable: Service not available.
> +# @invalid: Invalid handle.
> +# @error: Error with libdl (see 'msg').
> +#
> +# Since: 2.10
> +##
> +{ 'enum': 'InstrUnloadCode',
> + 'data': [ 'ok', 'unavailable', 'invalid', 'error' ] }
> +
> +##
> +# @InstrUnloadResult:
> +#
> +# Result of an 'instr-unload' command.
> +#
> +# @code: Result code.
> +# @msg: Additional error message.
Again, should msg be optional? Document that it is only for human
consumption.
> +#
> +# Since: 2.10
> +##
> +{ 'struct': 'InstrUnloadResult',
> + 'data': { 'code': 'InstrUnloadCode', 'msg': 'str' } }
> +
> +##
> +# @instr-unload:
> +#
> +# Unload an instrumentation library.
> +#
> +# @handle: Instrumentation library identifier (see #InstrLoadResult).
> +#
> +# Since: 2.10
> +##
> +{ 'command': 'instr-unload',
> + 'data': { 'handle': 'int' },
> + 'returns': 'InstrUnloadResult' }
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-07-24 18:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 17:02 [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation Lluís Vilanova
2017-07-24 17:06 ` [Qemu-devel] [PATCH 01/13] instrument: Add documentation Lluís Vilanova
2017-07-24 17:10 ` [Qemu-devel] [PATCH 02/13] instrument: [none] Add null instrumentation mode Lluís Vilanova
2017-07-24 17:14 ` [Qemu-devel] [PATCH 03/13] instrument: [dynamic] Add dynamic " Lluís Vilanova
2017-07-24 17:18 ` [Qemu-devel] [PATCH 04/13] instrument: Allow adding the "instrument" property without modifying event files Lluís Vilanova
2017-07-24 17:22 ` [Qemu-devel] [PATCH 05/13] instrument: [dynamic] Add default public per-event functions Lluís Vilanova
2017-07-24 17:26 ` [Qemu-devel] [PATCH 06/13] instrument: Add event control interface Lluís Vilanova
2017-07-24 17:30 ` [Qemu-devel] [PATCH 07/13] instrument: Add generic command line library loader Lluís Vilanova
2017-07-24 17:34 ` [Qemu-devel] [PATCH 08/13] instrument: [linux-user] Add " Lluís Vilanova
2017-07-24 17:38 ` [Qemu-devel] [PATCH 09/13] instrument: [bsd-user] " Lluís Vilanova
2017-07-24 17:42 ` [Qemu-devel] [PATCH 10/13] instrument: [softmmu] " Lluís Vilanova
2017-07-24 17:46 ` [Qemu-devel] [PATCH 11/13] instrument: [qapi] Add " Lluís Vilanova
2017-07-24 18:03 ` Eric Blake [this message]
2017-07-25 8:24 ` Lluís Vilanova
2017-07-25 11:30 ` Eric Blake
2017-07-25 11:51 ` Lluís Vilanova
2017-07-24 17:50 ` [Qemu-devel] [PATCH 12/13] instrument: [hmp] " Lluís Vilanova
2017-07-24 17:54 ` [Qemu-devel] [PATCH 13/13] trace: Rename C++-specific names in event arguments Lluís Vilanova
2017-07-25 13:19 ` [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation Stefan Hajnoczi
2017-07-25 13:30 ` Peter Maydell
2017-07-25 15:11 ` Lluís Vilanova
2017-07-26 11:22 ` Stefan Hajnoczi
2017-07-26 12:44 ` Lluís Vilanova
2017-07-27 10:32 ` Stefan Hajnoczi
2017-07-27 10:40 ` Peter Maydell
2017-07-28 13:42 ` Stefan Hajnoczi
2017-07-28 16:21 ` Lluís Vilanova
2017-08-02 11:04 ` Stefan Hajnoczi
2017-07-26 11:26 ` Stefan Hajnoczi
2017-07-26 11:49 ` Peter Maydell
2017-07-26 12:26 ` Lluís Vilanova
2017-07-27 10:43 ` Daniel P. Berrange
2017-07-27 10:54 ` Peter Maydell
2017-07-27 14:58 ` Lluís Vilanova
2017-07-27 15:21 ` Daniel P. Berrange
2017-07-27 15:33 ` Peter Maydell
2017-07-27 15:45 ` Daniel P. Berrange
2017-07-28 13:34 ` Stefan Hajnoczi
2017-07-28 13:41 ` Peter Maydell
2017-07-28 14:06 ` Daniel P. Berrange
2017-07-28 16:05 ` Lluís Vilanova
2017-08-01 13:48 ` Stefan Hajnoczi
2017-08-01 13:54 ` Peter Maydell
2017-08-02 11:04 ` Stefan Hajnoczi
2017-08-02 11:10 ` Peter Maydell
2017-08-02 14:49 ` Stefan Hajnoczi
2017-08-02 15:19 ` Lluís Vilanova
2017-08-03 11:54 ` Stefan Hajnoczi
2017-08-26 0:14 ` Emilio G. Cota
2017-08-26 0:02 ` Emilio G. Cota
2017-08-29 9:19 ` Peter Maydell
2017-07-28 13:52 ` Daniel P. Berrange
2017-07-28 16:14 ` Lluís Vilanova
2017-08-01 13:13 ` Stefan Hajnoczi
2017-07-28 15:10 ` Lluís Vilanova
2017-07-27 19:55 ` Lluís Vilanova
2017-07-25 14:47 ` Lluís Vilanova
2017-07-26 11:29 ` Stefan Hajnoczi
2017-07-26 12:31 ` Lluís Vilanova
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=109e1849-1bf6-5875-b304-7cacbf45f068@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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).