From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: y.karadz@gmail.com
Cc: rostedt@goodmis.org, linux-trace-devel@vger.kernel.org
Subject: [RFC PATCH v2 0/4] trace-cruncher: ftrace uprobes support
Date: Fri, 15 Apr 2022 07:10:08 +0300 [thread overview]
Message-ID: <20220415041012.36151-1-tz.stoyanov@gmail.com> (raw)
Ftrace uprobes can be used to create dynamic events for user functions.
Tracing user function can be very useful functionality for trace-cruncher.
v2 changes:
- Moved the uprobe C code into the ftrace-utils.c file.
- Reused internal functions from ftrace-util code.
- Renamed utrace start and stop to enable and disable, to be consistent
with the other APIs.
- Do not call utrace disable in the urtace example, as this logic is
triggered by the destructor.
- Changed the logic for allocation of internal dynamic array - double the
array size on each reallocation, instead of increasing the size with
hard-coded constant.
- Added support for running a program with arguments for tracing.
- Do not run the program for tracing in a separate shell.
- Coding style fixes and optimizations.
Tzvetomir Stoyanov (VMware) (4):
trace-cruncher: Logic for resolving address to function name
trace-cruncher: ftrace uprobe raw API
trace-cruncher: High level wrappers for ftrace uprobes
trace-cruncher: Example script for uprobes high level API
examples/user_trace.py | 43 ++
setup.py | 4 +-
src/ftracepy-utils.c | 676 ++++++++++++++++++++++++++++
src/ftracepy-utils.h | 21 +
src/ftracepy.c | 45 ++
src/trace-obj-debug.c | 982 +++++++++++++++++++++++++++++++++++++++++
src/trace-obj-debug.h | 54 +++
7 files changed, 1823 insertions(+), 2 deletions(-)
create mode 100755 examples/user_trace.py
create mode 100644 src/trace-obj-debug.c
create mode 100644 src/trace-obj-debug.h
--
2.35.1
next reply other threads:[~2022-04-15 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 4:10 Tzvetomir Stoyanov (VMware) [this message]
2022-04-15 4:10 ` [RFC PATCH v2 1/4] trace-cruncher: Logic for resolving address to function name Tzvetomir Stoyanov (VMware)
2022-04-18 9:13 ` Yordan Karadzhov
2022-04-15 4:10 ` [RFC PATCH v2 2/4] trace-cruncher: ftrace uprobe raw API Tzvetomir Stoyanov (VMware)
2022-04-15 4:10 ` [RFC PATCH v2 3/4] trace-cruncher: High level wrappers for ftrace uprobes Tzvetomir Stoyanov (VMware)
2022-04-18 11:54 ` Yordan Karadzhov
2022-04-19 8:22 ` Tzvetomir Stoyanov
2022-04-15 4:10 ` [RFC PATCH v2 4/4] trace-cruncher: Example script for uprobes high level API Tzvetomir Stoyanov (VMware)
2022-04-18 11:54 ` Yordan Karadzhov
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=20220415041012.36151-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=y.karadz@gmail.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).