From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 0/2] SysCall tracing
Date: Fri, 28 Jan 2022 20:21:00 +0200 [thread overview]
Message-ID: <20220128182102.8672-1-y.karadz@gmail.com> (raw)
Now, when we have the necessary APIs for working with 'eprobes' and
'synthetic' events, we can combine the two and trace system calls.
Yordan Karadzhov (VMware) (2):
trace-cruncher: Add (un)register methods for dynamic events
trace-cruncher: Add example of tracing systemcalls
examples/syscall_trace.py | 66 ++++++++++++++
src/ftracepy-utils.c | 90 ++++++++++++++-----
src/ftracepy-utils.h | 4 +
src/ftracepy.c | 15 +++-
tracecruncher/ft_utils.py | 2 +
.../tests/1_unit/test_01_ftracepy_unit.py | 7 +-
6 files changed, 159 insertions(+), 25 deletions(-)
create mode 100755 examples/syscall_trace.py
--
2.33.1
next reply other threads:[~2022-01-28 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:21 Yordan Karadzhov (VMware) [this message]
2022-01-28 18:21 ` [PATCH 1/2] trace-cruncher: Add (un)register methods for dynamic events Yordan Karadzhov (VMware)
2022-01-28 18:21 ` [PATCH 2/2] trace-cruncher: Add example of tracing systemcalls Yordan Karadzhov (VMware)
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=20220128182102.8672-1-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.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).