From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, michael.roth@amd.com, armbru@redhat.com,
vsementsov@virtuozzo.com, jsnow@redhat.com, hreitz@redhat.com,
kwolf@redhat.com, pbonzini@redhat.com
Subject: [PATCH v6 0/7] trace qmp commands
Date: Wed, 26 Jan 2022 17:11:23 +0100 [thread overview]
Message-ID: <20220126161130.3240892-1-vsementsov@virtuozzo.com> (raw)
This series aims to add trace points for each qmp command with help of
qapi code generator.
v6:
01-04,07: add Stefan's r-b
01: - subject changed
- rename:
gen_trace_events --> gen_tracing
_gen_trace_events --> _gen_tracing
_gent() --> _gen_trace_events()
- a bit more compact code for gent initializing
03: - rename:
gen_trace_events --> gen_tracing
_gen_trace_events --> _gen_tracing
04: fix --add-trace-events -> --gen-trace in commit message
05: - drop extra two sentences
- reword
- add example .trace-events file
06: reword
07: rename option to --suppress-tracing
Vladimir Sementsov-Ogievskiy (7):
qapi/gen: Add FOO.trace-events output module
qapi/commands: refactor error handling code
qapi/commands: Optionally generate trace for QMP commands
meson: generate trace events for qmp commands
docs/qapi-code-gen: update to cover trace events code generation
meson: document, why we don't generate trace events for tests/ and
qga/
qapi: generate trace events by default
docs/devel/qapi-code-gen.rst | 25 ++++++++-
meson.build | 3 ++
qapi/meson.build | 7 +++
qga/meson.build | 10 +++-
scripts/qapi/commands.py | 101 ++++++++++++++++++++++++++++++-----
scripts/qapi/gen.py | 31 +++++++++--
scripts/qapi/main.py | 14 +++--
tests/meson.build | 10 +++-
trace/meson.build | 11 ++--
9 files changed, 185 insertions(+), 27 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-26 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 16:11 Vladimir Sementsov-Ogievskiy [this message]
2022-01-26 16:11 ` [PATCH v6 1/7] qapi/gen: Add FOO.trace-events output module Vladimir Sementsov-Ogievskiy
2022-01-26 16:11 ` [PATCH v6 2/7] qapi/commands: refactor error handling code Vladimir Sementsov-Ogievskiy
2022-01-26 16:11 ` [PATCH v6 3/7] qapi/commands: Optionally generate trace for QMP commands Vladimir Sementsov-Ogievskiy
2022-01-27 7:24 ` Markus Armbruster
2022-01-27 9:42 ` Vladimir Sementsov-Ogievskiy
2022-01-26 16:11 ` [PATCH v6 4/7] meson: generate trace events for qmp commands Vladimir Sementsov-Ogievskiy
2022-01-26 16:11 ` [PATCH v6 5/7] docs/qapi-code-gen: update to cover trace events code generation Vladimir Sementsov-Ogievskiy
2022-01-27 8:20 ` Stefan Hajnoczi
2022-01-26 16:11 ` [PATCH v6 6/7] meson: document, why we don't generate trace events for tests/ and qga/ Vladimir Sementsov-Ogievskiy
2022-01-27 6:50 ` Markus Armbruster
2022-01-27 9:26 ` Vladimir Sementsov-Ogievskiy
2022-01-27 6:51 ` Markus Armbruster
2022-01-27 8:21 ` Stefan Hajnoczi
2022-01-26 16:11 ` [PATCH v6 7/7] qapi: generate trace events by default Vladimir Sementsov-Ogievskiy
2022-01-27 7:32 ` [PATCH v6 0/7] trace qmp commands Markus Armbruster
2022-01-27 9:41 ` Vladimir Sementsov-Ogievskiy
2022-01-27 11:10 ` Markus Armbruster
2022-01-27 8:21 ` Stefan Hajnoczi
2022-01-27 9:41 ` Vladimir Sementsov-Ogievskiy
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=20220126161130.3240892-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).