From: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
To: "linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: perf report does not resolve symbols on s390x
Date: Wed, 5 Jul 2017 16:45:49 +0200 [thread overview]
Message-ID: <eb00bf70-936d-e405-5867-015d4067202f@linux.vnet.ibm.com> (raw)
I use linux 4.12 kernel and the perf report --stdio does not resolve all symbols:
Only very few symbols are resolved and none listed in the call back chain.
Here is an example:
50.00% 50.00% true [kernel.vmlinux] [k] __rb_insert_augmented
|
---0x6a0624
0x2d7c00
0x2d79c8
0x2b5a26
0x2da542
0x2da01a
0x2d6c2e
0x2d6b86
50.00% 0.00% true [unknown] [k] 0x000000000011e90a
|
---0x11e90a
0x2d39a4
0x2d3238
0x288140
0x2cf404
0x2df5d8
0x31618c
0x19b0ae
These addresses are all in the /proc/kallsyms and valid.
When I do a perf script it works:
[root@s8360046 perf]# perf script
true 4384 7991.047063: 250000 cpu-clock:
19c0ae lock_acquire (/lib/modules/4.12.0perf+/build/vmlinux)
31718c lock_page_memcg (/lib/modules/4.12.0perf+/build/vmlinux)
2e05d8 page_add_file_rmap (/lib/modules/4.12.0perf+/build/vmlinux)
2d0404 alloc_set_pte (/lib/modules/4.12.0perf+/build/vmlinux)
289140 filemap_map_pages (/lib/modules/4.12.0perf+/build/vmlinux)
2d4238 __handle_mm_fault (/lib/modules/4.12.0perf+/build/vmlinux)
2d49a4 handle_mm_fault (/lib/modules/4.12.0perf+/build/vmlinux)
11f90a do_dat_exception (/lib/modules/4.12.0perf+/build/vmlinux)
6a1962 pgm_check_handler (/lib/modules/4.12.0perf+/build/vmlinux)
Any ideas in which area of the perf report tool to dig into to get this fixed.
When I use -vvvvv I see all kernel symbols read in and listed, so I fail to see
why they are not resolved.
Maybe someone can point me to the area of code to start digging.
Thanks a lot.
--
Thomas Richter, Dept 3303, IBM LTC Boeblingen Germany
--
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next reply other threads:[~2017-07-05 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 14:45 Thomas-Mich Richter [this message]
2017-07-05 15:50 ` perf report does not resolve symbols on s390x Arnaldo Carvalho de Melo
2017-07-06 7:23 ` Thomas-Mich Richter
2017-07-06 12:35 ` Thomas-Mich Richter
2017-07-07 12:17 ` Thomas-Mich Richter
2017-07-07 12:22 ` Arnaldo Carvalho de Melo
2017-07-11 19:03 ` Arnaldo Carvalho de Melo
2017-07-11 19:38 ` Arnaldo Carvalho de Melo
2017-07-11 19:48 ` Arnaldo Carvalho de Melo
2017-07-12 8:21 ` Thomas-Mich Richter
2017-07-12 10:40 ` Michael Ellerman
2017-07-12 14:04 ` Arnaldo Carvalho de Melo
2017-07-13 12:02 ` Michael Ellerman
2017-07-12 9:05 ` Thomas-Mich Richter
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=eb00bf70-936d-e405-5867-015d4067202f@linux.vnet.ibm.com \
--to=tmricht@linux.vnet.ibm.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).