From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
don <zds100@gmail.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mhiramat@kernel.org
Subject: [PATCH v3 0/5] tracing/probes: Support tracepoint events on modules
Date: Sun, 18 Aug 2024 19:42:49 +0900 [thread overview]
Message-ID: <172397776900.286558.8986646398199362026.stgit@devnote2> (raw)
Hi,
This is the 3rd version of the raw tracepoint events on modules.
The previous version is here;
https://lore.kernel.org/all/fbfec8d9-d0ed-4384-bbd2-dd5c1e568ed1@efficios.com/
This version supports tracepoint event on unloaded modules according
to Mathies' suggestion ([2/5],[4/5] and part of [5/5]) .
The concern about blocking module unload by instrumentation is TBD.
Note, to support tracepoints in the unloaded modules, tracepoint event
can not check the given tracepoint is really defined or not. So unless
CONFIG_MODULES=n, it does not check the tracepoint existence. IOW,
user can specify any tracepoint name for tracepoint events. It will be
just ignored.
You can download this series from;
https://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git topic/tprobe-on-module
Thank you,
---
Masami Hiramatsu (Google) (5):
tracepoint: Support iterating over tracepoints on modules
tracepoint: Support tterating tracepoints in a loading module
tracing/fprobe: Support raw tracepoint events on modules
tracing/fprobe: Support raw tracepoints on future loaded modules
sefltests/tracing: Add a test for tracepoint events on modules
include/linux/tracepoint.h | 20 ++
kernel/trace/trace_fprobe.c | 179 +++++++++++++++-----
kernel/tracepoint.c | 42 +++++
tools/testing/selftests/ftrace/config | 1
.../test.d/dynevent/add_remove_tprobe_module.tc | 61 +++++++
.../ftrace/test.d/dynevent/tprobe_syntax_errors.tc | 1
6 files changed, 254 insertions(+), 50 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/add_remove_tprobe_module.tc
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2024-08-18 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 10:42 Masami Hiramatsu (Google) [this message]
2024-08-18 10:42 ` [PATCH v3 1/5] tracepoint: Support iterating over tracepoints on modules Masami Hiramatsu (Google)
2024-08-18 10:43 ` [PATCH v3 2/5] tracepoint: Support tterating tracepoints in a loading module Masami Hiramatsu (Google)
2024-09-11 0:21 ` Masami Hiramatsu
2024-08-18 10:43 ` [PATCH v3 3/5] tracing/fprobe: Support raw tracepoint events on modules Masami Hiramatsu (Google)
2024-08-18 10:43 ` [PATCH v3 4/5] tracing/fprobe: Support raw tracepoints on future loaded modules Masami Hiramatsu (Google)
2024-08-18 10:43 ` [PATCH v3 5/5] sefltests/tracing: Add a test for tracepoint events on modules Masami Hiramatsu (Google)
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=172397776900.286558.8986646398199362026.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=zds100@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).