linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Paul Mackerras <paulus@samba.org>
Subject: [GIT PULL] perf updates
Date: Fri,  5 Mar 2010 22:55:47 +0100	[thread overview]
Message-ID: <1267826147-6613-1-git-send-regression-fweisbec@gmail.com> (raw)

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(-)

             reply	other threads:[~2010-03-05 21:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 21:55 Frederic Weisbecker [this message]
2010-03-10 14:28 ` [GIT PULL] perf updates Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2019-09-26 20:06 Ingo Molnar
2019-09-26 23:00 ` pr-tracker-bot
2016-08-06  6:05 Ingo Molnar
2016-05-25 20:18 Ingo Molnar
2015-07-04 11:25 Ingo Molnar
2015-04-18 15:22 Ingo Molnar
2013-11-13 20:58 Ingo Molnar
2012-05-23 19:01 Ingo Molnar
2011-02-26 15:11 [PATCH v2] perf: Fix undefined PyVarObject_HEAD_INIT in python 2.5 Frederic Weisbecker
2011-03-04  0:38 ` [GIT PULL] perf updates Frederic Weisbecker
2011-03-04  7:10   ` Ingo Molnar
2010-06-08 20:13 Frederic Weisbecker
2010-06-08 21:13 ` Ingo Molnar
2010-05-25 13:45 Frederic Weisbecker
2010-05-09 20:43 Frederic Weisbecker
2010-05-10  5:10 ` Frederic Weisbecker
2010-05-10  6:46 ` Ingo Molnar
2010-04-14 15:59 Frederic Weisbecker
2010-04-04 14:36 Frederic Weisbecker
2010-04-04 14:42 ` Frederic Weisbecker
2010-04-04 19:02   ` Ingo Molnar
2010-04-05  9:56   ` Hitoshi Mitake
2010-03-03  6:54 Frederic Weisbecker
2010-02-27 18:25 [GIT PULL] Perf updates Frederic Weisbecker
2009-12-14 16:24 [GIT PULL] perf updates Ingo Molnar

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=1267826147-6613-1-git-send-regression-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).