From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Subject: [for-next][PATCH 0/6] tracing: Event probes for 5.15
Date: Sat, 21 Aug 2021 10:29:04 -0400 [thread overview]
Message-ID: <20210821142904.655644298@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 297e1dcdca3d7f268ccfb175d0a3534bb9481303
Steven Rostedt (VMware) (5):
selftests/ftrace: Add clear_dynamic_events() to test cases
selftests/ftrace: Fix requirement check of README file
selftests/ftrace: Add test case to test adding and removing of event probe
selftests/ftrace: Add selftest for testing eprobe events on synthetic 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 | 8 -
kernel/trace/trace_probe.c | 16 +-
kernel/trace/trace_probe.h | 6 +-
.../ftrace/test.d/dynevent/add_remove_eprobe.tc | 40 +
.../ftrace/test.d/dynevent/test_duplicates.tc | 38 +
tools/testing/selftests/ftrace/test.d/functions | 24 +-
.../inter-event/trigger-synthetic-eprobe.tc | 53 ++
13 files changed, 1116 insertions(+), 14 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
create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-synthetic-eprobe.tc
next reply other threads:[~2021-08-21 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 14:29 Steven Rostedt [this message]
2021-08-21 14:29 ` [for-next][PATCH 1/6] tracing: Add a probe that attaches to trace events Steven Rostedt
2021-08-21 14:29 ` [for-next][PATCH 2/6] selftests/ftrace: Add clear_dynamic_events() to test cases Steven Rostedt
2021-08-21 14:29 ` [for-next][PATCH 3/6] selftests/ftrace: Fix requirement check of README file Steven Rostedt
2021-08-21 14:29 ` [for-next][PATCH 4/6] selftests/ftrace: Add test case to test adding and removing of event probe Steven Rostedt
2021-08-21 14:29 ` [for-next][PATCH 5/6] selftests/ftrace: Add selftest for testing eprobe events on synthetic events Steven Rostedt
2021-08-21 14:29 ` [for-next][PATCH 6/6] selftests/ftrace: Add selftest for testing duplicate eprobes and kprobes 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=20210821142904.655644298@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tz.stoyanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.