From: Jiri Olsa <jolsa@redhat.com>
To: rostedt@goodmis.org, fweisbec@gmail.com, a.p.zijlstra@chello.nl
Cc: linux-kernel@vger.kernel.org
Subject: [RFC 0/4] trace,perf: Enabling ftrace:function tracepoint for perf
Date: Mon, 11 Jul 2011 15:22:52 +0200 [thread overview]
Message-ID: <1310390576-8289-1-git-send-email-jolsa@redhat.com> (raw)
hi,
attached patches add perf support for function trace.
- Patch 1 adds support to register ftrace:function tracepoint.
- Patch 2 adds a way to used filtering for ip and parent_ip fields.
- Patches 3 and 4 are adding new ioctl to specify the filter on the
"struct ftrace" level.
I know this is probably not a good idea, but I dont see a good way
to combine ftrace_ops filtering with tracepoint filtering other than
keep them separated.
My other guess is instead of ioctl use some keyword to specify functions
followed by standard filter.. something like:
"FUNCTION_TRACE(sys_open sys_close sys_read) (ip == sys_open)"
Please take this more as a question about interface than forcing
new ioctl.. ;)
attached patches:
- 1/4 perf, ftrace: Add perf support to use function tracepoint
- 2/4 perf, ftrace: Add filter support
- 3/4 perf, ftrace: Add new perf ioctl for function trace filter
- 4/4 perf, ftrace: Add ftrace option for perf stat command
thanks for comments,
jirka
---
include/linux/ftrace.h | 7 +-
include/linux/ftrace_event.h | 9 +-
include/linux/perf_event.h | 2 +
kernel/events/core.c | 14 +++
kernel/trace/ftrace.c | 34 +++++-
kernel/trace/trace.h | 5 +
kernel/trace/trace_event_perf.c | 225 +++++++++++++++++++++++++++++-------
kernel/trace/trace_events.c | 10 +-
kernel/trace/trace_events_filter.c | 32 ++++-
kernel/trace/trace_export.c | 21 ++++
kernel/trace/trace_kprobe.c | 6 +-
kernel/trace/trace_syscalls.c | 14 ++-
tools/perf/builtin-stat.c | 2 +
tools/perf/util/evlist.c | 26 ++++-
tools/perf/util/evlist.h | 2 +
tools/perf/util/evsel.h | 1 +
tools/perf/util/parse-events.c | 37 ++++++-
tools/perf/util/parse-events.h | 1 +
18 files changed, 376 insertions(+), 72 deletions(-)
next reply other threads:[~2011-07-11 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 13:22 Jiri Olsa [this message]
2011-07-11 13:22 ` [RFC 1/4] perf, ftrace: Add perf support to use function tracepoint Jiri Olsa
2011-07-11 13:22 ` [RFC 2/4] perf, ftrace: Add filter support for ftrace:function tracepoint Jiri Olsa
2011-08-10 19:34 ` Steven Rostedt
2011-07-11 13:22 ` [RFC 3/4] perf, ftrace: Add new perf ioctl for function trace filter Jiri Olsa
2011-07-18 15:12 ` Frederic Weisbecker
2011-07-19 9:57 ` Jiri Olsa
2011-07-26 13:43 ` Frederic Weisbecker
2011-07-27 12:17 ` Jiri Olsa
2011-08-10 20:25 ` Steven Rostedt
2011-07-11 13:22 ` [RFC 4/4] perf, ftrace: Add ftrace option for perf stat command Jiri Olsa
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=1310390576-8289-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®