[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100310142826.GA7848@elte.hu>
Date: Wed, 10 Mar 2010 15:28:26 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Paul Mackerras <paulus@...ba.org>
Subject: Re: [GIT PULL] perf updates
* Frederic Weisbecker <fweisbec@...il.com> wrote:
> Ingo,
>
> Please pull the perf/core branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> perf/core
>
> - Lock events seem to be usable now with perf
> - Better performances in x86-64 stacktraces
> - Trace events now have correct callchains
> - Cleanups
>
>
> Other patches still in discussion are not in the branch.
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (5):
> lockdep: Move lock events under lockdep recursion protection
> perf/x86-64: Use frame pointer to walk on irq and process stacks
> perf: Introduce new perf_fetch_caller_regs() for hot regs snapshot
> perf: Take a hot regs snapshot for trace events
> perf: Drop the obsolete profile naming for trace events
>
>
> arch/x86/kernel/cpu/perf_event.c | 12 +++
> arch/x86/kernel/dumpstack.h | 15 +++
> arch/x86/kernel/dumpstack_64.c | 4 +-
> include/linux/ftrace_event.h | 23 +++--
> include/linux/perf_event.h | 42 +++++++++-
> include/linux/syscalls.h | 24 +++---
> include/trace/ftrace.h | 44 +++++-----
> include/trace/syscall.h | 8 +-
> kernel/lockdep.c | 9 +--
> kernel/perf_event.c | 18 ++--
> kernel/trace/Makefile | 2 +-
> kernel/trace/trace_event_perf.c | 165 ++++++++++++++++++++++++++++++++++++
> kernel/trace/trace_event_profile.c | 164 -----------------------------------
> kernel/trace/trace_events.c | 2 +-
> kernel/trace/trace_kprobe.c | 29 +++---
> kernel/trace/trace_syscalls.c | 72 ++++++++--------
> 16 files changed, 353 insertions(+), 280 deletions(-)
Pulled, thanks a lot Frederic!
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists