From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>, Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH 3/3] perf top: Support userspace symbols too
Date: Tue, 27 Oct 2009 14:00:00 +0100 [thread overview]
Message-ID: <20091027130000.GA32628@elte.hu> (raw)
In-Reply-To: <1256592199-9608-3-git-send-email-acme@redhat.com>
* Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> Example:
>
> Compiling the kernel with 'make -k 22 allyesconfig'
>
> [root@emilia linux-2.6-tip]# perf top -r 90
> ------------------------------------------------------------------------------
> PerfTop: 3669 irqs/sec kernel:59.9% [1000Hz cycles], (all, 8 CPUs)
> ------------------------------------------------------------------------------
>
> samples pcnt function DSO
> _______ _____ ________________________________ ________________
>
> 3062.00 6.5% clear_page_c [kernel]
> 2233.00 4.8% _int_malloc /lib64/libc-2.5.so
> 2100.00 4.5% yylex /home/acme/git/build/allyesconfig/scripts/genksyms/genksyms
> 2029.00 4.3% memset /lib64/libc-2.5.so
> 1224.00 2.6% page_fault [kernel]
> 1075.00 2.3% __GI_strlen /lib64/libc-2.5.so
> 863.00 1.8% sub_preempt_count [kernel]
> 822.00 1.8% __GI_memcpy /lib64/libc-2.5.so
> 810.00 1.7% __GI_vfprintf /lib64/libc-2.5.so
> 786.00 1.7% _int_free /lib64/libc-2.5.so
> 775.00 1.7% __GI_strcmp /lib64/libc-2.5.so
> 748.00 1.6% _spin_lock [kernel]
> 699.00 1.5% main /home/acme/git/build/allyesconfig/scripts/basic/fixdep
> 659.00 1.4% add_preempt_count [kernel]
> 649.00 1.4% yyparse /home/acme/git/build/allyesconfig/scripts/genksyms/genksyms
> 645.00 1.4% preempt_trace [kernel]
> 635.00 1.4% __GI___libc_free /lib64/libc-2.5.so
> 597.00 1.3% trace_preempt_on [kernel]
> 551.00 1.2% __GI___libc_malloc /lib64/libc-2.5.so
> 516.00 1.1% _spin_lock_irqsave [kernel]
> 481.00 1.0% copy_user_generic_string [kernel]
> 479.00 1.0% unmap_vmas [kernel]
> 429.00 0.9% _IO_file_xsputn_internal /lib64/libc-2.5.so
> 425.00 0.9% __GI_strncpy /lib64/libc-2.5.so
> 416.00 0.9% get_page_from_freelist [kernel]
> 414.00 0.9% malloc_consolidate /lib64/libc-2.5.so
> 406.00 0.9% get_parent_ip [kernel]
> 362.00 0.8% __rmqueue [kernel]
> 347.00 0.7% in_lock_functions [kernel]
> 316.00 0.7% __d_lookup [kernel]
>
> [root@emilia linux-2.6-tip]#
That's a really nice feature! I tried it and works well here too.
Ingo
next prev parent reply other threads:[~2009-10-27 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 21:23 [PATCH 1/3] perf record: process can disappear while reading its /proc/pid/tasks Arnaldo Carvalho de Melo
2009-10-26 21:23 ` [PATCH 2/3] perf tools: Generalize event synthesizing routines Arnaldo Carvalho de Melo
2009-10-26 21:23 ` [PATCH 3/3] perf top: Support userspace symbols too Arnaldo Carvalho de Melo
2009-10-27 13:00 ` Ingo Molnar [this message]
2009-10-27 13:04 ` [tip:perf/core] " tip-bot for Arnaldo Carvalho de Melo
2009-10-27 13:03 ` [tip:perf/core] perf tools: Generalize event synthesizing routines tip-bot for Arnaldo Carvalho de Melo
2009-10-27 13:03 ` [tip:perf/core] perf record: Fix race where process can disappear while reading its /proc/pid/tasks tip-bot for Arnaldo Carvalho de Melo
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=20091027130000.GA32628@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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