linux-kernel - Re: [PATCH 3/3] perf top: Support userspace symbols too

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Oct 2009 14:00:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Paul Mackerras <paulus@...ba.org>,
	Mike Galbraith <efault@....de>
Subject: Re: [PATCH 3/3] perf top: Support userspace symbols too


* Arnaldo Carvalho de Melo <acme@...hat.com> wrote:

> Example:
> 
> Compiling the kernel with 'make -k 22 allyesconfig'
> 
> [root@...lia 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@...lia linux-2.6-tip]#

That's a really nice feature! I tried it and works well here too.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/