linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lin Ming <minggr@gmail.com>
To: zhao bao <baozhao@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf trace cannot work with software events ?
Date: Sat, 26 Mar 2011 17:28:54 +0800	[thread overview]
Message-ID: <AANLkTikXKDiyf7Q=mY_ez2P3OSw23VaRMdKcF_M-KCc0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=pRKpdupEcXS0FmOA-PiAiXHWPYwWxN4F27fFC@mail.gmail.com>

On Sat, Mar 26, 2011 at 4:04 PM, zhao bao <baozhao@gmail.com> wrote:
>  Hi,  I want to trace page faults in my program. The result I wanted like this:
>  1st page fault at addrA.
>  2nd page fault at addrB.
>  3rd page fault at addrC
>  ...
>
>  Perf seems providing this function, but I can't get what I want.
>  I use Perf on Fedora 14(kernel 2.6.35). The following is what I have
> done in my machine.
> Thanks for help in advance.
>
> [root@localhost lab]# perf record -R -c 1  -d  -e  faults ./hello

It's used to trace kernel space page faults, not for userspace code.

Lin Ming

> hello,world
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.010 MB perf.data (~418 samples) ]
>
> [root@localhost lab]# perf trace
>  Fatal: no event_list!
> --
> 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-26  9:28 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 [this message]
     [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
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='AANLkTikXKDiyf7Q=mY_ez2P3OSw23VaRMdKcF_M-KCc0@mail.gmail.com' \
    --to=minggr@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).