All of lore.kernel.org
 help / color / mirror / Atom feed
From: leroy christophe <christophe.leroy@c-s.fr>
To: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Strange reports of perf events on powerpc 83xx
Date: Thu, 27 Aug 2015 15:58:59 +0200	[thread overview]
Message-ID: <55DF17A3.7070009@c-s.fr> (raw)

Hi,

Has anybody already used 'perf' tool on powerpc MPC83xx ?

I have been succesfully using perf on MPC8xx, but on MPC83xx I get 
something strange.

perf record/report reports addresses on user stack, as if it was mixing 
up D accesses and I accesses.

Any idea of what the problem can be ?

# Samples: 8K of event 'cpu-clock'
# Event count (approx.): 2196000000
#
# Overhead  Command       Shared Object       Symbol
# ........  ............  .................. 
............................................
#
      2.62%  perf_reseau4  libpthread-2.18.so  [.] __libc_send
      2.56%  perf_reseau4  [kernel.kallsyms]   [k] __ip_make_skb
      1.62%  perf_reseau4  [kernel.kallsyms]   [k] __ip_append_data.isra.39
      1.55%  perf_reseau4  [kernel.kallsyms]   [k] ip_finish_output
      1.33%  perf_reseau4  [unknown]           [k] 0x7ffffd94
      1.33%  perf_reseau4  [unknown]           [k] 0x7ffffd95
      1.28%  perf_reseau4  [unknown]           [k] 0x7ffffd97
      1.26%  perf_reseau4  [unknown]           [k] 0x7ffffda3
      1.24%  perf_reseau4  [unknown]           [k] 0x7ffffd98
      1.22%  perf_reseau4  [unknown]           [k] 0x7ffffd92
      1.22%  perf_reseau4  [unknown]           [k] 0x7ffffd9b
      1.22%  perf_reseau4  [unknown]           [k] 0x7ffffdaa
      1.21%  perf_reseau4  [unknown]           [k] 0x7ffffd96
      1.18%  perf_reseau4  [unknown]           [k] 0x7ffffda7
      1.17%  perf_reseau4  [unknown]           [k] 0x7ffffd8d
      1.17%  perf_reseau4  [unknown]           [k] 0x7ffffd99
      1.13%  perf_reseau4  [unknown]           [k] 0x7ffffd90
      1.13%  perf_reseau4  [unknown]           [k] 0x7ffffda2
      1.12%  perf_reseau4  [kernel.kallsyms]   [k] __local_bh_enable_ip
      1.12%  perf_reseau4  [unknown]           [k] 0x7ffffd9c
      1.12%  perf_reseau4  [unknown]           [k] 0x7ffffd9e
      1.10%  perf_reseau4  [unknown]           [k] 0x7ffffda0
      1.08%  perf_reseau4  [unknown]           [k] 0x7ffffd9f
      1.08%  perf_reseau4  [unknown]           [k] 0x7ffffda6
      1.05%  perf_reseau4  [unknown]           [k] 0x7ffffda8
      1.02%  perf_reseau4  [unknown]           [k] 0x7ffffd9a
      1.01%  perf_reseau4  [unknown]           [k] 0x7ffffdb0
      1.00%  perf_reseau4  [unknown]           [k] 0x7ffffd89
      1.00%  perf_reseau4  [unknown]           [k] 0x7ffffd8b
      1.00%  perf_reseau4  [unknown]           [k] 0x7ffffdac


Christophe

             reply	other threads:[~2015-08-27 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 13:58 leroy christophe [this message]
2015-09-02 14:20 ` Strange reports of perf events on powerpc 83xx Joakim Tjernlund
2015-09-02 14:20   ` Joakim Tjernlund
2015-09-02 18:48   ` christophe leroy
  -- strict thread matches above, loose matches on Subject: below --
2015-08-29 14:34 christophe leroy

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=55DF17A3.7070009@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.