From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH 0/3] ftrace: Event probe updates
Date: Mon, 1 Aug 2022 11:32:05 +0900 [thread overview]
Message-ID: <165932112555.2850673.7704483936633223533.stgit@devnote2> (raw)
This series adds some features/tests to event probe, which includes
- Add event probe syntax error logs on <tracefs>/error_log file.
- Add 'if' filter to the event probe.
- Add a syntax error test case for event probe.
'if' filter is a new feature, which allows us to define new event based on
the condition. There are some events which include both start and end
events by one event type. e.g. CPU idle (power/cpu_idle) event is called
at the CPU idle start with "state=C-state ID" and at the end with "state=(u32)-1".
In that case, it is useful if we can define 2 new event probes on it for
the start and the end besed on the state value. Or, we can classify events
based on running CPU, etc.
Thanks,
---
Masami Hiramatsu (Google) (3):
tracing/eprobe: Show syntax error logs in error_log file
tracing/eprobe: Add eprobe filter support
selftests/ftrace: Add eprobe syntax error testcase
kernel/trace/trace_eprobe.c | 115 ++++++++++++++++++--
kernel/trace/trace_probe.h | 6 +
.../test.d/dynevent/eprobes_syntax_errors.tc | 27 +++++
3 files changed, 137 insertions(+), 11 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/eprobes_syntax_errors.tc
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2022-08-01 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 2:32 Masami Hiramatsu (Google) [this message]
2022-08-01 2:32 ` [PATCH 1/3] tracing/eprobe: Show syntax error logs in error_log file Masami Hiramatsu (Google)
2022-08-01 2:32 ` [PATCH 2/3] tracing/eprobe: Add eprobe filter support Masami Hiramatsu (Google)
2022-08-01 20:57 ` Steven Rostedt
2022-11-09 3:33 ` Rafael Mendonca
2022-11-12 2:14 ` Masami Hiramatsu
2022-11-12 5:23 ` Masami Hiramatsu
2022-08-01 2:32 ` [PATCH 3/3] selftests/ftrace: Add eprobe syntax error testcase 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=165932112555.2850673.7704483936633223533.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox