LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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 v9 0/6] tracing: Creation of event probe
Date: Fri, 20 Aug 2021 16:46:44 -0400	[thread overview]
Message-ID: <20210820204644.546662591@goodmis.org> (raw)


V8 Link: https://lore.kernel.org/linux-trace-devel/20210819152604.704335282@goodmis.org/

Changes from v8:

Found and fixed a bug in the selftests that check the README file.
I was testing that requirement with eprobes, and found that it was not
flagging it as not added. Found the reason, and fixed it.

Changed the selftest for add/remove of the eprobe to just add test
and remove it.

Moved the selftest that added a eprobe to a synthetic event into the trigger
tests.

Have the "testing duplicate" not test kprobes if kprobes are not configured
in.

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

             reply	other threads:[~2021-08-20 20:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 20:46 Steven Rostedt [this message]
2021-08-20 20:46 ` [PATCH v9 1/6] tracing: Add a probe that attaches to trace events Steven Rostedt
2021-08-20 20:46 ` [PATCH v9 2/6] selftests/ftrace: Add clear_dynamic_events() to test cases Steven Rostedt
2021-08-20 20:46 ` [PATCH v9 3/6] selftests/ftrace: Fix requirement check of README file Steven Rostedt
2021-08-21  1:43   ` Masami Hiramatsu
2021-08-20 20:46 ` [PATCH v9 4/6] selftests/ftrace: Add test case to test adding and removing of event probe Steven Rostedt
2021-08-21  1:40   ` Masami Hiramatsu
2021-08-20 20:46 ` [PATCH v9 5/6] selftests/ftrace: Add selftest for testing eprobe events on synthetic events Steven Rostedt
2021-08-21  1:38   ` Masami Hiramatsu
2021-08-20 20:46 ` [PATCH v9 6/6] selftests/ftrace: Add selftest for testing duplicate eprobes and kprobes Steven Rostedt
2021-08-21  1:41   ` Masami Hiramatsu
2021-08-21  2:18     ` 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=20210820204644.546662591@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 \
    --subject='Re: [PATCH v9 0/6] tracing: Creation of event probe' \
    /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

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).