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>,
Anton Blanchard <anton@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/3] perfcounter: callchain symbol resolving and fixes
Date: Wed, 1 Jul 2009 05:35:12 +0200 [thread overview]
Message-ID: <1246419315-9968-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
This patchset provides the symbol resolving for callchains.
Example:
perf report -s sym -c
5.40% [k] __d_lookup
3.60%
__d_lookup
perf_callchain
perf_counter_overflow
intel_pmu_handle_irq
perf_counter_nmi_handler
notifier_call_chain
atomic_notifier_call_chain
notify_die
do_nmi
nmi
do_lookup
__link_path_walk
path_walk
do_path_lookup
user_path_at
vfs_fstatat
vfs_lstat
sys_newlstat
system_call_fastpath
__lxstat
0x406fb1
1.26%
__d_lookup
perf_callchain
perf_counter_overflow
intel_pmu_handle_irq
perf_counter_nmi_handler
notifier_call_chain
atomic_notifier_call_chain
notify_die
do_nmi
nmi
do_lookup
__link_path_walk
path_walk
do_path_lookup
user_path_at
vfs_fstatat
vfs_lstat
sys_newlstat
system_call_fastpath
__lxstat
[...]
Sorry about the third patch, it's a kind of all-in-one monolithic thing which
gathers various fixes. I should have granulate it...
Still in my plans:
- 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 another one:
- remove the perfcounter internal nmi call frame (ie: every nmi frame)
so that we drop this header from each callchain:
perf_callchain
perf_counter_overflow
intel_pmu_handle_irq
perf_counter_nmi_handler
notifier_call_chain
atomic_notifier_call_chain
notify_die
do_nmi
nmi
Frederic.
Frederic Weisbecker (3):
perfcounter: Fix storage size allocation of callchain list
perfcounter: Resolve symbols in callchains
perfcounter: Various fixes for callchains
tools/perf/builtin-report.c | 102 ++++++++++++++++++++++-----------
tools/perf/util/callchain.c | 131 ++++++++++++++++++++++++++++++++-----------
tools/perf/util/callchain.h | 5 +-
3 files changed, 168 insertions(+), 70 deletions(-)
next reply other threads:[~2009-07-01 3:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 3:35 Frederic Weisbecker [this message]
2009-07-01 3:35 ` [PATCH 1/3] perfcounter: Fix storage size allocation of callchain list Frederic Weisbecker
2009-07-01 8:46 ` [tip:perfcounters/urgent] perf_counter tools: " tip-bot for Frederic Weisbecker
2009-07-01 3:35 ` [PATCH 2/3] perfcounter: Resolve symbols in callchains Frederic Weisbecker
2009-07-01 8:46 ` [tip:perfcounters/urgent] perf_counter tools: " tip-bot for Frederic Weisbecker
2009-07-01 3:35 ` [PATCH 3/3] perfcounter: Various fixes for callchains Frederic Weisbecker
2009-07-01 8:46 ` [tip:perfcounters/urgent] perf_counter tools: " tip-bot for Frederic Weisbecker
2009-07-01 8:18 ` [PATCH 0/3] perfcounter: callchain symbol resolving and fixes Ingo Molnar
2009-07-01 16:33 ` Frederic Weisbecker
2009-07-01 17:14 ` Frederic Weisbecker
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=1246419315-9968-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=anton@samba.org \
--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
all inboxes | Powered by JetHome®