From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 0/9] [GIT PULL] perf/tracing: fixes and add function trace to perf
Date: Wed, 22 Feb 2012 09:40:36 -0500 [thread overview]
Message-ID: <20120222144036.824378742@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
Ingo,
Please pull the latest tip/perf/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/core
Head SHA1: 5500fa51199aee770ce53718853732600543619e
Andrey Vagin (1):
tracing: Don't print an extra separator of flags
Jiri Olsa (7):
ftrace: Add enable/disable ftrace_ops control interface
ftrace, perf: Add open/close tracepoint perf registration actions
ftrace, perf: Add add/del tracepoint perf registration actions
ftrace: Add FTRACE_ENTRY_REG macro to allow event registration
ftrace, perf: Add support to use function tracepoint in perf
ftrace: Allow to specify filter field type for ftrace events
ftrace, perf: Add filter support for function trace event
Steven Rostedt (1):
tracing: Don't use p->len field to determine output in __print_*() functions
----
include/linux/ftrace.h | 73 ++++++++++++-
include/linux/ftrace_event.h | 9 ++-
include/linux/perf_event.h | 3 +
kernel/trace/ftrace.c | 117 +++++++++++++++++++--
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_output.c | 12 ++-
kernel/trace/trace_syscalls.c | 18 +++-
13 files changed, 667 insertions(+), 117 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-02-22 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 14:40 Steven Rostedt [this message]
2012-02-22 14:40 ` [PATCH 1/9] tracing: Dont print an extra separator of flags Steven Rostedt
2012-02-22 14:40 ` [PATCH 2/9] tracing: Dont use p->len field to determine output in __print_*() functions Steven Rostedt
2012-02-22 14:40 ` [PATCH 3/9] ftrace: Add enable/disable ftrace_ops control interface Steven Rostedt
2012-02-22 14:40 ` [PATCH 4/9] ftrace, perf: Add open/close tracepoint perf registration actions Steven Rostedt
2012-02-22 14:40 ` [PATCH 5/9] ftrace, perf: Add add/del " Steven Rostedt
2012-02-22 14:40 ` [PATCH 6/9] ftrace: Add FTRACE_ENTRY_REG macro to allow event registration Steven Rostedt
2012-02-22 14:40 ` [PATCH 7/9] ftrace, perf: Add support to use function tracepoint in perf Steven Rostedt
2012-02-22 14:40 ` [PATCH 8/9] ftrace: Allow to specify filter field type for ftrace events Steven Rostedt
2012-02-22 14:40 ` [PATCH 9/9] ftrace, perf: Add filter support for function trace event 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=20120222144036.824378742@goodmis.org \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.