From: David Ahern <dsahern@gmail.com>
To: zhao bao <baozhao@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Fwd: perf trace cannot work with software events ?
Date: Sat, 26 Mar 2011 21:59:01 -0600 [thread overview]
Message-ID: <4D8EB605.7070407@gmail.com> (raw)
In-Reply-To: <AANLkTik4RrEh8wgj+TXB1DYZtfn1Wp3iMiZs-XZBrsRG@mail.gmail.com>
On 03/26/11 10:13, zhao bao wrote:
> Follow your guide, I git the latest kernel and compiled the perf tools
> , then perf script works.
> But I found the outputed address is instruction address, not the
> address caused the page fault. Can I get these addresses with perf
> tool?
> [root@localhost lab]# /root/bin/perf script
> hello 30242 [000] 48324.304652: page-faults:
> c05b6d35 clear_user ([kernel.kallsyms])
> hello 30242 [000] 48324.304684: page-faults:
> c05b6d35 clear_user ([kernel.kallsyms])
> hello 30242 [000] 48324.304701: page-faults:
> c05b68a0 __copy_to_user_ll ([kernel.kallsyms])
> hello 30242 [000] 48324.304746: page-faults:
> 870 _start (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304750: page-faults:
> 4920 _dl_start (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304753: page-faults:
> 17acb __i686.get_pc_thunk.bx (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304755: page-faults:
> 4939 _dl_start (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304765: page-faults:
> a790 _dl_setup_hash (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304768: page-faults:
> 14480 _dl_sysdep_start (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304771: page-faults:
> 14560 _dl_sysdep_start (/lib/ld-2.13.so)
> hello 30242 [000] 48324.304774: page-faults:
> 159e0 brk (/lib/ld-2.13.so)
Without callchains it shows the IP when the event triggered. If you want
more detail try adding -g to perf-record to get callchains.
next prev parent reply other threads:[~2011-03-27 3:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 8:04 perf trace cannot work with software events ? zhao bao
2011-03-26 9:28 ` Lin Ming
[not found] ` <AANLkTi=VrazJpV+dpzX2hWJ8dYDgbdo_5FAOMRYRo0GD@mail.gmail.com>
2011-03-26 12:31 ` Fwd: " zhao bao
2011-03-26 13:13 ` David Ahern
2011-03-26 14:00 ` zhao bao
2011-03-26 14:23 ` David Ahern
2011-03-26 16:13 ` zhao bao
2011-03-27 3:59 ` David Ahern [this message]
2011-03-27 7:44 ` zhao bao
2011-03-27 21:09 ` David Ahern
2011-03-29 15:48 ` zhao bao
2011-03-29 16:55 ` baozhao
2011-03-29 20:05 ` David Ahern
2011-04-18 3:43 ` perf trace Kumar Ranjit-B04060
2011-04-18 6:08 ` David Ahern
2011-04-18 6:38 ` Kumar Ranjit-B04060
2011-04-18 6:48 ` David Ahern
2011-04-18 17:46 ` Kumar Ranjit-B04060
2011-04-18 19:26 ` David Ahern
2011-03-29 17:07 ` Fwd: perf trace cannot work with software events ? zhao bao
2011-03-26 14:27 ` Lin Ming
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=4D8EB605.7070407@gmail.com \
--to=dsahern@gmail.com \
--cc=baozhao@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).