public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Questions] How to run 'perf top' on ARM to profile kernel functions with modules loaded
Date: Thu, 11 Nov 2010 09:28:43 +0100	[thread overview]
Message-ID: <20101111082843.GA32728@elte.hu> (raw)
In-Reply-To: <AANLkTim+BAYKWqiJzSQQLc4e_yNkMsNNnEp5u8YgC2Fk@mail.gmail.com>


* Ming Lei <tom.leiming@gmail.com> wrote:

> 2010/11/11 Ming Lei <tom.leiming@gmail.com>:
> > Hi,
> >
> > 'perf top' can't display any functions when modules are loaded on ARM.
> 
> Sorry, should be can't display any kernel functions when modules are loaded
> on ARM.
> 
> Also, when modules are loaded, 'perf report' can't display functions names,
> follows result of 'perf report':
> 
> root@beagleboard:~# perf report
> # Events: 4K cycles
> #
> # Overhead      Command      Shared Object                  Symbol
> # ........  ...........  .................  ......................
> #
>     97.36%      swapper  [musb_hdrc]        [k]  10466c4
>      2.19%         perf  [musb_hdrc]        [k]  10da070
>      0.09%  ksoftirqd/0  [musb_hdrc]        [k]  10db998
>      0.06%         perf  libc-2.9.so        [.] memchr
>      0.04%         perf  libc-2.9.so        [.]    663c0
>      0.02%         perf  perf               [.]     2e80
>      0.02%         perf  libc-2.9.so        [.] closedir
>      0.02%         perf  libc-2.9.so        [.] __read
>      0.02%  flush-179:0  [musb_hdrc]        [k]  10ff124
>      0.02%         perf  libc-2.9.so        [.] memset
>      0.02%         perf  libc-2.9.so        [.] __memcpy_chk
>      0.02%         perf  perf               [.] event__synthesize_comm
>      0.02%         perf           ffff0fc4  [.] ffff0fc4
>      0.02%         perf  perf               [.] hex2u64
>      0.02%         perf  libc-2.9.so        [.] _IO_vfprintf
>      0.02%         perf  libc-2.9.so        [.] fgets
>      0.02%         perf  libpthread-2.9.so  [.] flockfile
>      0.02%         perf  perf               [.] kallsyms__parse
>      0.02%         perf  libc-2.9.so        [.] _IO_getline_info
> 
> Any suggestions or comments?

Must be some bug in the ELF symbol handling code - we've had many cases of quirks 
and special cases there. Please run 'perf archive' and send the resulting 
perf.data.tar.bz2 to Arnaldo in private mail. (the file will be big)

Thanks,

	Ingo

  reply	other threads:[~2010-11-11  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  6:56 [Questions] How to run 'perf top' on ARM to profile kernel functions with modules loaded Ming Lei
2010-11-11  7:52 ` Ming Lei
2010-11-11  8:28   ` Ingo Molnar [this message]
2010-11-11  8:34   ` Kyungmin Park
2010-11-11 10:03     ` Ming Lei
2010-11-11  9:17   ` Jamie Iles
2010-11-11 12:06     ` Peter Zijlstra
2010-11-11 12:21       ` Jamie Iles
2010-11-11 12:30         ` Peter Zijlstra
2010-11-12  1:40           ` Ming Lei

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=20101111082843.GA32728@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paulus@samba.org \
    --cc=tom.leiming@gmail.com \
    /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