From: Jiri Olsa <jolsa@redhat.com>
To: rostedt@goodmis.org, fweisbec@gmail.com, mingo@redhat.com,
paulus@samba.org, acme@ghostprotocols.net,
a.p.zijlstra@chello.nl
Cc: linux-kernel@vger.kernel.org, aarapov@redhat.com
Subject: [PATCHv9 0/7] ftrace, perf: Adding support to use function trace
Date: Wed, 15 Feb 2012 15:51:47 +0100 [thread overview]
Message-ID: <1329317514-8131-1-git-send-email-jolsa@redhat.com> (raw)
hi,
here's another version of perf support for function trace
with filter.
attached patches:
- 1/7 ftrace: Add enable/disable ftrace_ops control interface
- 2/7 ftrace, perf: Add open/close tracepoint perf registration actions
- 3/7 ftrace, perf: Add add/del tracepoint perf registration actions
- 4/7 ftrace: Add FTRACE_ENTRY_REG macro to allow event registration
- 5/7 ftrace, perf: Add support to use function tracepoint in perf
- 6/7 ftrace: Allow to specify filter field type for ftrace events
- 7/7 ftrace, perf: Add filter support for function trace event
v9 changes:
fixed patches 5/7 and 7/7 to work with disabled options:
CONFIG_FUNCTION_TRACER, CONFIG_DYNAMIC_FTRACE
thanks,
jirka
---
include/linux/ftrace.h | 77 +++++++++++++-
include/linux/ftrace_event.h | 9 ++-
include/linux/perf_event.h | 3 +
kernel/trace/ftrace.c | 132 ++++++++++++++++++++---
kernel/trace/trace.h | 38 +++++--
kernel/trace/trace_entries.h | 54 +++++++---
kernel/trace/trace_event_perf.c | 208 ++++++++++++++++++++++++++++-------
kernel/trace/trace_events.c | 12 ++-
kernel/trace/trace_events_filter.c | 168 ++++++++++++++++++++++++++++-
kernel/trace/trace_export.c | 64 ++++++++----
kernel/trace/trace_kprobe.c | 8 ++-
kernel/trace/trace_syscalls.c | 18 +++-
12 files changed, 671 insertions(+), 120 deletions(-)
next reply other threads:[~2012-02-15 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 14:51 Jiri Olsa [this message]
2012-02-15 14:51 ` [PATCH 1/7] ftrace: Add enable/disable ftrace_ops control interface Jiri Olsa
2012-02-27 9:33 ` [tip:perf/core] ftrace: Add enable/ disable " tip-bot for Jiri Olsa
2012-02-15 14:51 ` [PATCH 2/7] ftrace, perf: Add open/close tracepoint perf registration actions Jiri Olsa
2012-02-27 9:34 ` [tip:perf/core] ftrace, perf: Add open/ close " tip-bot for Jiri Olsa
2012-02-15 14:51 ` [PATCH 3/7] ftrace, perf: Add add/del " Jiri Olsa
2012-02-27 9:34 ` [tip:perf/core] ftrace, perf: Add add/ del " tip-bot for Jiri Olsa
2012-02-15 14:51 ` [PATCH 4/7] ftrace: Add FTRACE_ENTRY_REG macro to allow event registration Jiri Olsa
2012-02-15 15:13 ` Frederic Weisbecker
2012-02-27 9:35 ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-02-15 14:51 ` [PATCH 5/7] ftrace, perf: Add support to use function tracepoint in perf Jiri Olsa
2012-02-15 16:03 ` Frederic Weisbecker
2012-02-27 9:36 ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-02-15 14:51 ` [PATCH 6/7] ftrace: Allow to specify filter field type for ftrace events Jiri Olsa
2012-02-27 9:37 ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-02-15 14:51 ` [PATCH 7/7] ftrace, perf: Add filter support for function trace event Jiri Olsa
2012-02-27 9:38 ` [tip:perf/core] " tip-bot for 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=1329317514-8131-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarapov@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).