public inbox for linux-kernel@vger.kernel.org
 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 <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Paul Mackerras <paulus@samba.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: [GIT PULL] perf callchain improvement and fixes
Date: Sun, 22 Aug 2010 23:15:37 +0200	[thread overview]
Message-ID: <1282511740-22631-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

Unfortunately we were missing a lot of callchains in multithread
cases. And this was not a regression, it was rather the fact I
was missing a part of the histogram processing: the collapsing.

Anyway, this is eventually fixed. Thanks a lot to Chistoph Hellwig
who reported this.

Thanks,
	Frederic
---

Frederic Weisbecker (3):
      perf: Keep track of the max depth of a callchain
      perf: Rename append_callchain into callchain_append
      perf: Support for callchains merge


 tools/perf/builtin-report.c |    3 +-
 tools/perf/util/callchain.c |   98 ++++++++++++++++++++++++++++++++++---------
 tools/perf/util/callchain.h |   25 +++++++----
 tools/perf/util/hist.c      |    4 +-
 tools/perf/util/sort.h      |    2 +-
 5 files changed, 100 insertions(+), 32 deletions(-)

             reply	other threads:[~2010-08-22 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22 21:15 Frederic Weisbecker [this message]
2010-08-22 21:15 ` [PATCH 1/3] perf: Keep track of the max depth of a callchain Frederic Weisbecker
2010-08-22 21:15 ` [PATCH 2/3] perf: Rename append_callchain into callchain_append Frederic Weisbecker
2010-08-22 21:15 ` [PATCH 3/3] perf: Support for callchains merge Frederic Weisbecker
2010-08-23  9:20 ` [GIT PULL] perf callchain improvement and fixes 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=1282511740-22631-1-git-send-regression-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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