From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/3] Initial trace-cmd support for ftrace uprobes
Date: Wed, 16 Sep 2020 14:47:06 +0300 [thread overview]
Message-ID: <20200916114709.291533-1-tz.stoyanov@gmail.com> (raw)
Ftrace supports uprobes - trace events on user space applications.
Trace-cmd cannot configure uprobes, in order to support it this new
functionality is introduced:
- Function name to file offset mapping, this information is extracted
from the dwarf and ELF headers in the binary file.
- New options are added to "trace-cmd record" for setting a uprobe:
--uprobe file:function
--uprobe-ret file:function
Tzvetomir Stoyanov (VMware) (3):
trace-cmd: Internal refactoring of pid address map logic
trace-cmd: New internal APIs for reading ELF header
trace-cmd: [POC] Add support for uprobes
Makefile | 10 +
include/trace-cmd/trace-cmd.h | 9 +
tracecmd/Makefile | 2 +
tracecmd/include/trace-local.h | 49 +-
tracecmd/trace-obj-debug.c | 823 +++++++++++++++++++++++++++++++++
tracecmd/trace-record.c | 193 ++++----
tracecmd/trace-uprobes.c | 221 +++++++++
tracecmd/trace-usage.c | 4 +
8 files changed, 1197 insertions(+), 114 deletions(-)
create mode 100644 tracecmd/trace-obj-debug.c
create mode 100644 tracecmd/trace-uprobes.c
--
2.26.2
next reply other threads:[~2020-09-16 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 11:47 Tzvetomir Stoyanov (VMware) [this message]
2020-09-16 11:47 ` [PATCH v2 1/3] trace-cmd: Internal refactoring of pid address map logic Tzvetomir Stoyanov (VMware)
2020-09-16 11:47 ` [PATCH v2 2/3] trace-cmd: New internal APIs for reading ELF header Tzvetomir Stoyanov (VMware)
2020-09-17 13:42 ` Steven Rostedt
2020-09-16 11:47 ` [PATCH v2 3/3] trace-cmd: [POC] Add support for uprobes Tzvetomir Stoyanov (VMware)
2020-09-16 13:26 ` [PATCH v2 0/3] Initial trace-cmd support for ftrace uprobes Steven Rostedt
2020-09-17 1:07 ` Steven Rostedt
2020-09-24 7:14 Tzvetomir Stoyanov (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=20200916114709.291533-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).