[PATCH 00/15] [GIT PULL] tracing: updates for 2.6.39

From: Steven Rostedt
Date: Thu Mar 10 2011 - 11:02:43 EST



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-2.6-trace.git
tip/perf/core


David Sharp (8):
tracing: Add an 'overwrite' trace_option.
ring-buffer: Remove unused #include <linux/trace_irq.h>
tracing: Fix event alignment: ftrace:context_switch and ftrace:wakeup
tracing: Fix event alignment: module:module_request
tracing: Fix event alignment: kvm:kvm_hv_hypercall
tracing: Fix event alignment: mce:mce_record
tracing: Fix event alignment: skb:kfree_skb
tracing: Adjust conditional expression latency formatting.

Jiri Olsa (1):
tracing: Explain about unstable clock on resume with ring buffer warning

Steven Rostedt (5):
tracing: Remove lock_depth from event entry
ftrace: Add .ref.text as one of the safe areas to trace
ftrace/graph: Trace function entry before updating index
tracing: Align 4 byte ints together in struct tracer
tracing: Fix irqoff selftest expanding max buffer

Yuanhan Liu (1):
tracing: Export trace_set_clr_event()

----
Documentation/trace/ftrace.txt | 5 +++++
arch/x86/kernel/ftrace.c | 15 ++++++++-------
arch/x86/kvm/trace.h | 8 ++++----
include/linux/ftrace_event.h | 1 -
include/linux/ring_buffer.h | 2 ++
include/trace/events/mce.h | 8 ++++----
include/trace/events/module.h | 5 ++---
include/trace/events/skb.h | 4 ++--
kernel/trace/ring_buffer.c | 24 +++++++++++++++++++++---
kernel/trace/trace.c | 34 +++++++++++++++++++++++-----------
kernel/trace/trace.h | 3 ++-
kernel/trace/trace_entries.h | 6 +++---
kernel/trace/trace_events.c | 2 +-
kernel/trace/trace_output.c | 36 ++++++++++++++++++++----------------
scripts/recordmcount.c | 3 ++-
scripts/recordmcount.pl | 1 +
16 files changed, 100 insertions(+), 57 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/