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 07:13:57 -0600 [thread overview]
Message-ID: <4D8DE695.3000606@gmail.com> (raw)
In-Reply-To: <AANLkTi=A5hkUE0xna5zmuXGt=LvMS_C41whzwM0-nUNs@mail.gmail.com>
On 03/26/11 06:31, zhao bao wrote:
>> It's used to trace kernel space page faults, not for userspace code.
>>
>> Lin Ming
>>
>
> From the ouput of "perf report" command, I think perf can record the
> page faults from userspace code.
>
> [root@localhost lab]# perf record -R -c 1 -d -e faults ./hello
> hello,world
'-e faults' is a software event. perf-trace does not handle S/W events.
perf-trace has been renamed to perf-script, and perf-script recently
gained the ability to dump S/W events:
https://lkml.org/lkml/2011/3/10/3
David
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.010 MB perf.data (~420 samples) ]
> [root@localhost lab]# perf report
> # Events: 92 cycles
> #
> # Overhead Command Shared Object Symbol
> # ........ ....... ................. ......
> #
> 10.87% hello ld-2.12.90.so [.] .L198
> 6.52% hello ld-2.12.90.so [.] _dl_load_cache_lookup
> 6.52% hello ld-2.12.90.so [.] _dl_lookup_symbol_x
> 4.35% hello ld-2.12.90.so [.] dl_main
> 3.26% hello ld-2.12.90.so [.] _dl_start
> 3.26% hello ld-2.12.90.so [.] _dl_cache_libcmp
> 3.26% hello ld-2.12.90.so [.] do_lookup_x
> 2.17% hello libc-2.12.90.so [.] _init
> 2.17% hello libc-2.12.90.so [.] _IO_file_overflow_internal
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-26 13:13 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 [this message]
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
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=4D8DE695.3000606@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).