From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Tzvetomir Stoyanov" <tz.stoyanov@gmail.com>,
Tom Zanussi <zanussi@kernel.org>
Subject: [PATCH v8 0/5] tracing: Creation of event probe
Date: Thu, 19 Aug 2021 11:26:04 -0400 [thread overview]
Message-ID: <20210819152604.704335282@goodmis.org> (raw)
V7 Link: https://lore.kernel.org/linux-trace-devel/20210819041321.105110033@goodmis.org/
Changes from v7:
I moved the patches that have been acked by Masami into my linux-next queue
and removed them from this patch series.
I added Masami's patch to check for duplicate events and return a proper
error message about the duplication.
I changed the duplication check in the eprobe code to match Masami's
changes.
I fixed a bug in the removing of dynamic events in the selftest code.
Added a new test to make sure the duplicate events are caught.
Masami Hiramatsu (1):
tracing/probes: Reject events which have the same name of existing one
Steven Rostedt (VMware) (3):
selftests/ftrace: Add clear_dynamic_events() to test cases
selftests/ftrace: Add selftest for testing eprobe events
selftests/ftrace: Add selftest for testing duplicate eprobes and kprobes
Tzvetomir Stoyanov (VMware) (1):
tracing: Add a probe that attaches to trace events
----
include/linux/trace_events.h | 4 +
kernel/trace/Makefile | 1 +
kernel/trace/trace.c | 5 +-
kernel/trace/trace.h | 18 +
kernel/trace/trace_eprobe.c | 903 +++++++++++++++++++++
kernel/trace/trace_events_trigger.c | 14 +-
kernel/trace/trace_kprobe.c | 14 +-
kernel/trace/trace_probe.c | 41 +-
kernel/trace/trace_probe.h | 7 +-
kernel/trace/trace_uprobe.c | 6 +-
.../ftrace/test.d/dynevent/add_remove_eprobe.tc | 53 ++
.../ftrace/test.d/dynevent/test_duplicates.tc | 28 +
tools/testing/selftests/ftrace/test.d/functions | 22 +
13 files changed, 1101 insertions(+), 15 deletions(-)
create mode 100644 kernel/trace/trace_eprobe.c
create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc
next reply other threads:[~2021-08-19 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 15:26 Steven Rostedt [this message]
2021-08-19 15:26 ` [PATCH v8 1/5] tracing/probes: Reject events which have the same name of existing one Steven Rostedt
2021-08-19 15:26 ` [PATCH v8 2/5] tracing: Add a probe that attaches to trace events Steven Rostedt
2021-08-20 0:10 ` Masami Hiramatsu
2021-08-19 15:26 ` [PATCH v8 3/5] selftests/ftrace: Add clear_dynamic_events() to test cases Steven Rostedt
2021-08-20 0:13 ` Masami Hiramatsu
2021-08-19 15:26 ` [PATCH v8 4/5] selftests/ftrace: Add selftest for testing eprobe events Steven Rostedt
2021-08-20 0:46 ` Masami Hiramatsu
2021-08-20 14:08 ` Steven Rostedt
2021-08-19 15:26 ` [PATCH v8 5/5] selftests/ftrace: Add selftest for testing duplicate eprobes and kprobes Steven Rostedt
2021-08-20 0:53 ` Masami Hiramatsu
2021-08-20 14:13 ` 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=20210819152604.704335282@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=tz.stoyanov@gmail.com \
--cc=zanussi@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).