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 v3 0/3] trace qmp commands
Date: Mon, 17 Jan 2022 21:18:42 +0100 [thread overview]
Message-ID: <20220117201845.2438382-1-vsementsov@virtuozzo.com> (raw)
Hi all!
This series aims to add trace points for each qmp command with help of
qapi code generator.
v3:
- don't drop old trace events
- make pair of qmp_enter_ and qmp_exit_ trace events
- improve patch splitting
- use term "trace events" constantly instead of "trace points"
- add comment on subdir ordering to last commit
Vladimir Sementsov-Ogievskiy (3):
scripts/qapi/gen.py: add .trace-events file for module
scripts/qapi-gen.py: add --add-trace-events option
meson: generate trace events for qmp commands
meson.build | 5 +++
qapi/meson.build | 9 +++-
scripts/qapi/commands.py | 91 ++++++++++++++++++++++++++++++++++------
scripts/qapi/gen.py | 13 ++++--
scripts/qapi/main.py | 10 +++--
trace/meson.build | 11 +++--
6 files changed, 116 insertions(+), 23 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-17 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 20:18 Vladimir Sementsov-Ogievskiy [this message]
2022-01-17 20:18 ` [PATCH v3 1/3] scripts/qapi/gen.py: add .trace-events file for module Vladimir Sementsov-Ogievskiy
2022-01-18 8:38 ` Markus Armbruster
2022-01-18 10:34 ` Vladimir Sementsov-Ogievskiy
2022-01-17 20:18 ` [PATCH v3 2/3] scripts/qapi-gen.py: add --add-trace-events option Vladimir Sementsov-Ogievskiy
2022-01-18 10:27 ` Markus Armbruster
2022-01-18 11:58 ` Vladimir Sementsov-Ogievskiy
2022-01-18 14:22 ` Markus Armbruster
2022-01-19 8:41 ` Paolo Bonzini
2022-01-17 20:18 ` [PATCH v3 3/3] meson: generate trace events for qmp commands Vladimir Sementsov-Ogievskiy
2022-01-18 10:30 ` Markus Armbruster
2022-01-18 12:21 ` Paolo Bonzini
2022-01-18 13:05 ` Markus Armbruster
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=20220117201845.2438382-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 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.