From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/2] perfcounter: callchains with perf report
Date: Fri, 26 Jun 2009 16:27:59 +0200 [thread overview]
Message-ID: <1246026481-8314-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
Here is a first shot for the sorted callchains per entries handling
with per report.
I'll continue to improve it:
- symbol resolution
- profit we have a tree to display a better graph hierarchy
- let the user provide a limit for hit percentage, depth, number of
backtraces, etc...
- better output
- colors
- and so on....
Thanks.
Frederic Weisbecker (2):
perfcounter: prepare a small callchain framework
perfcounter: print sorted callchains per histogram entries
tools/perf/Makefile | 1 +
tools/perf/builtin-report.c | 87 +++++++++++++++++----
tools/perf/perf.h | 5 +
tools/perf/util/callchain.c | 174 +++++++++++++++++++++++++++++++++++++++++++
tools/perf/util/callchain.h | 33 ++++++++
5 files changed, 284 insertions(+), 16 deletions(-)
create mode 100644 tools/perf/util/callchain.c
create mode 100644 tools/perf/util/callchain.h
next reply other threads:[~2009-06-26 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 14:27 Frederic Weisbecker [this message]
2009-06-26 14:28 ` [PATCH 1/2] perfcounter: prepare a small callchain framework Frederic Weisbecker
2009-06-26 15:51 ` [tip:perfcounters/urgent] perf_counter tools: Prepare " tip-bot for Frederic Weisbecker
2009-06-26 14:28 ` [PATCH 2/2] perfcounter: print sorted callchains per histogram entries Frederic Weisbecker
2009-06-26 15:52 ` [tip:perfcounters/urgent] perf report: Print " tip-bot for Frederic Weisbecker
2009-06-26 14:48 ` [PATCH 0/2] perfcounter: callchains with perf report Ingo Molnar
2009-06-27 1:12 ` Paul Mackerras
2009-06-28 21:05 ` Frederic Weisbecker
2009-06-28 23:40 ` Paul Mackerras
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=1246026481-8314-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--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
Powered by JetHome