linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: baozhao <baozhao@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Fwd: perf trace cannot work with software events ?
Date: Tue, 29 Mar 2011 14:05:33 -0600	[thread overview]
Message-ID: <4D923B8D.1020204@gmail.com> (raw)
In-Reply-To: <loom.20110329T185259-431@post.gmane.org>



On 03/29/11 10:55, baozhao wrote:
> zhao bao <baozhao <at> gmail.com> writes:
> 
> 
>> I applyed this patch in the builtin-script.c , recompile and install
>> it. But I found it still doesn't  show any CR2 address info. The patch
>> seems to list a addr column, but perf script still work as before.
> 
>  Hi, I think I find the problem.
> In builtin-script.c,   array output_fields should also be
> changed,PERF_OUTPUT_ADDR should added to  [PERF_TYPE_SOFTWARE],  am I
> right?

The defaults do need to better detect when it exists. Until then you can
add addr to the --fields option.


> 
> static u64 output_fields[PERF_TYPE_MAX] = {
>        ....
>       [PERF_TYPE_SOFTWARE] = PERF_OUTPUT_COMM | PERF_OUTPUT_TID | \
>                               PERF_OUTPUT_CPU | PERF_OUTPUT_TIME | \
>                               PERF_OUTPUT_EVNAME | PERF_OUTPUT_SYM | \
>                               PERF_OUTPUT_ADDR,
> 
> 
> Here is the output:
> [root@localhost lab]#  /root/bin/perf script
>           hello  2229 [000]  1339.388865: page-faults: 0x804963c
>   c05ccbb3 clear_user ([kernel.kallsyms])
>           hello  2229 [000]  1339.388898: page-faults: 0x670834
>  c05ccbb3 clear_user ([kernel.kallsyms])
>           hello  2229 [000]  1339.388915: page-faults: 0xbf905d6b
>    c05cc70c __copy_to_user_ll ([kernel.kallsyms])
>           hello  2229 [000]  1339.388945: page-faults: 0x652870
>       870 _start (/lib/ld-2.13.so)
>           hello  2229 [000]  1339.388950: page-faults: 0x656920
>      4920 _dl_start (/lib/ld-2.13.so)
>           hello  2229 [000]  1339.388954: page-faults: 0x669acb
>     17acb __i686.get_pc_thunk.bx (/lib/ld-2.13.so)
>           hello  2229 [000]  1339.388958: page-faults: 0x66fe54
>      4939 _dl_start (/lib/ld-2.13.so)

And per another thread we can look at converting the sample addresses to
symbols/dsos.

David


> 
> 
> 
> 
> --
> 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

  reply	other threads:[~2011-03-29 20:05 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
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 [this message]
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=4D923B8D.1020204@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).