linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Taras Glek <tglek@mozilla.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: How to use perf to log page faults
Date: Wed, 12 May 2010 21:59:49 +0200	[thread overview]
Message-ID: <20100512195945.GE10028@nowhere> (raw)
In-Reply-To: <4BEB03B6.6080706@mozilla.com>

On Wed, May 12, 2010 at 12:38:30PM -0700, Taras Glek wrote:
> Hi,
> From the docs it seems that perf may be useful for logging page faults.  
> I tried
> perf record -g -d -f -e page-faults <mycommand>
> but all I got were PERF_RECORD_MMAP events.
>
> I'm using 2.6.32. Ideally I'd like to collect fault addresses and  
> userspace stacks that caused them. Isn't this what the page-fault event  
> is for?
>
> Taras


Could you try with -c 1 ?

Otherwise, does that work on the latest kernel?

Thanks.


  reply	other threads:[~2010-05-12 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 19:38 How to use perf to log page faults Taras Glek
2010-05-12 19:59 ` Frederic Weisbecker [this message]
2010-05-12 21:18   ` Taras Glek
2010-05-12 21:29     ` Frederic Weisbecker
2010-05-12 20:07 ` Andi Kleen

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=20100512195945.GE10028@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglek@mozilla.com \
    /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).