Re: [PATCH 00/10] [GIT PULL] for tip/tracing/core

From: Ingo Molnar
Date: Tue Apr 07 2009 - 07:56:32 EST



* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> Ingo,
>
> These are the same patches I sent out earlier, but I rebased them
> to tip/tracing/core. I also changed my S-o-B to be
> rostedt@xxxxxxxxxxx since I prefer email going to that address
> instead.
>
> -- Steve
>
> Please pull the latest tip/tracing/core tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core
>
>
> Frederic Weisbecker (2):
> tracing/ftrace: fix missing include string.h
> tracing/ftrace: factorize the tracing files creation
>
> Huang Weiyi (1):
> tracing, x86: remove duplicated #include
>
> Lai Jiangshan (1):
> tracing: fix incorrect return type of ns2usecs() V2
>
> Li Zefan (1):
> tracing: use macros to denote usec and nsec per second
>
> Steven Rostedt (3):
> tracing: remove CALLER_ADDR2 from wakeup tracer
> function-graph: add proper initialization for init task
> function-graph: use int instead of atomic for ftrace_graph_active
>
> Zhaolei (2):
> ftrace: Add check of sched_stopped for probe_sched_wakeup
> ftrace: Clean up enable logic for sched_switch
>
> ----
> arch/x86/kernel/ftrace.c | 1 -
> include/linux/ftrace.h | 8 ++-
> include/linux/init_task.h | 2 +
> kernel/trace/ftrace.c | 53 ++++--------
> kernel/trace/ring_buffer.c | 7 +-
> kernel/trace/trace.c | 163 ++++++++++++++----------------------
> kernel/trace/trace.h | 8 ++-
> kernel/trace/trace_boot.c | 5 +-
> kernel/trace/trace_event_profile.c | 3 +-
> kernel/trace/trace_mmiotrace.c | 6 +-
> kernel/trace/trace_output.c | 2 +-
> kernel/trace/trace_printk.c | 6 +-
> kernel/trace/trace_sched_switch.c | 11 ++-
> kernel/trace/trace_sched_wakeup.c | 8 ++-
> kernel/trace/trace_stack.c | 13 +--
> kernel/trace/trace_sysprof.c | 6 +-
> 16 files changed, 128 insertions(+), 174 deletions(-)

Pulled, thanks Steve!

Ingo
--
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/