From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 0/3] libtracefs: Facilitate adding and removing kprobes
Date: Tue, 29 Jun 2021 16:53:23 -0400 [thread overview]
Message-ID: <20210629205326.117059-1-rostedt@goodmis.org> (raw)
Add a tracefs_kprobe_raw() to facilitate adding kprobe events. It's
denoted as "raw" because it still requires knowing the complex format of
a kprobe, but at least it helps with other formats:
p:[[system/]event] addr fmt
The user only needs to know the "fmt" part above, and not worry about
what file to open, or how to open it.
Also add a tracefs_kprobe_clear() to clear all kprobes and a
tracefs_kprobe_clear_probe() to clear an individual kprobe. Both have a
"force" parameter, that if set, will then try to disable the kprobe in
all instances (including the top) and then remove the kprobe(s).
(Man pages coming after this).
Steven Rostedt (VMware) (3):
libtracefs: Implement tracefs_kprobe_raw()
libtracefs: Implement tracefs_kprobe_clear() to remove all kprobes
libtracefs: Implement tracefs_kprobe_clear_probe()
include/tracefs.h | 5 +
src/Makefile | 1 +
src/tracefs-kprobes.c | 242 ++++++++++++++++++++++++++++++++++++++++++
3 files changed, 248 insertions(+)
create mode 100644 src/tracefs-kprobes.c
--
2.30.2
next reply other threads:[~2021-06-29 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 20:53 Steven Rostedt [this message]
2021-06-29 20:53 ` [PATCH 1/3] libtracefs: Implement tracefs_kprobe_raw() Steven Rostedt
2021-06-29 20:53 ` [PATCH 2/3] libtracefs: Implement tracefs_kprobe_clear() to remove all kprobes Steven Rostedt
2021-06-29 20:53 ` [PATCH 3/3] libtracefs: Implement tracefs_kprobe_clear_probe() Steven Rostedt
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=20210629205326.117059-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--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).