Re: [PATCH 00/15] [GIT PULL] tracing: Updates for 3.5

From: Steven Rostedt
Date: Fri May 18 2012 - 21:43:35 EST


On Fri, 2012-05-18 at 09:08 -0400, Steven Rostedt wrote:
> Ingo,
>
> This should be my last set of changes for the next merge window.

Not quite :-)

You can hold off on pulling this. I want to add Masami's Acked-by tag,
and Vaibhav gave me two more patches. I'll run it through my own tests
and then do another pull request.

Thanks!

-- Steve

>
> 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: b732d439cb43336cd6d7e804ecb2c81193ef63b0
>
>
> Namhyung Kim (1):
> tracing: Check return value of tracing_dentry_percpu()
>
> Steven Rostedt (11):
> tracing: Clean up tracing_mark_write()
> ring-buffer: Add integrity check at end of iter read
> ring-buffer: Reset head page before running self test
> ftrace: Sort all function addresses, not just per page
> ftrace: Remove extra helper functions
> ftrace: Speed up search by skipping pages by address
> ftrace: Consolidate ftrace_location() and ftrace_text_reserved()
> ftrace: Return record ip addr for ftrace_location()
> ftrace: Make ftrace_modify_all_code() global for archs to use
> ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()
> ftrace: Remove selecting FRAME_POINTER with FUNCTION_TRACER
>
> Vaibhav Nagarnaik (3):
> ring-buffer: Make removal of ring buffer pages atomic
> ring-buffer: Make addition of pages in ring buffer atomic
> tracing: change CPU ring buffer state from tracing_cpumask
>
> ----
> arch/x86/kernel/ftrace.c | 15 +-
> include/asm-generic/vmlinux.lds.h | 2 +-
> include/linux/ftrace.h | 5 +-
> kernel/trace/Kconfig | 1 -
> kernel/trace/ftrace.c | 198 ++++++++++---------
> kernel/trace/ring_buffer.c | 394 +++++++++++++++++++++++++++++--------
> kernel/trace/trace.c | 49 ++---
> 7 files changed, 446 insertions(+), 218 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/