linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Chao Xu <caesarxuchao@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf record always record the same kernel symbol
Date: Fri, 10 May 2013 14:22:42 -0600	[thread overview]
Message-ID: <518D5712.5070907@gmail.com> (raw)
In-Reply-To: <CAKZq+rcx8qAmU8ZW8QTcrw3sd28-_5kbo6e5qXZuKqSAjYEm2Q@mail.gmail.com>

On 5/10/13 1:58 PM, Chao Xu wrote:
> Thanks David. This indeed gave more samples. Do you know why the symbol
>   [k] 0xffffffff81043fea occured so often? As shown in the pasted
> result, both "swapper" and "perf" had this symbol. And if I "perf record
> dd if=/dev/zero of=/dev/null" or "perf record ping", they all showed
> this symbol. I pasted these results in the end of this email.
> I guess my real concern is the symbols cannot be mapped into meaningful
> function names. These symbols cannot be found in either /proc/kallsyms
> nor the vmlinux I built from the kernel source tree. Any idea? Thanks.

take a look at the output of report -v and report -D. For me those 
commands work just fine:

# perf record -a -- sleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.104 MB perf.data (~4527 samples) ]

# perf report

  38.39%       swapper  [kernel.kallsyms]   [k] intel_idle
   9.26%          perf  [kernel.kallsyms]   [k] generic_exec_single
   5.58%       swapper  [kernel.kallsyms]   [k] cpuidle_wrap_enter
   4.73%       swapper  [kernel.kallsyms]   [k] hpet_legacy_next_event
   4.47%       swapper  [kernel.kallsyms]   [k] _raw_spin_lock_irqsave
...

David

  parent reply	other threads:[~2013-05-10 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 19:04 perf record always record the same kernel symbol Chao Xu
2013-05-10 19:12 ` David Ahern
     [not found]   ` <CAKZq+rcx8qAmU8ZW8QTcrw3sd28-_5kbo6e5qXZuKqSAjYEm2Q@mail.gmail.com>
2013-05-10 20:22     ` David Ahern [this message]
2013-05-10 20:43   ` Chao Xu

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=518D5712.5070907@gmail.com \
    --to=dsahern@gmail.com \
    --cc=caesarxuchao@gmail.com \
    --cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).