public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: perf_counters: page fault trace record
Date: Sat, 13 Jun 2009 12:09:16 +0200	[thread overview]
Message-ID: <20090613100916.GA9959@elte.hu> (raw)
In-Reply-To: <18995.28357.164575.925080@cargo.ozlabs.ibm.com>


* Paul Mackerras <paulus@samba.org> wrote:

> Corey Ashford writes:
> 
> > Paul Mackerras wrote:
> > > Can't you do what you need just using a page fault software 
> > > counter with sample_type = PERF_SAMPLE_IP | PERF_SAMPLE_ADDR 
> > > and sample_period = 1?
> > 
> > I thought about that, but I was under the (incorrect?) 
> > impression that on Power, the PERF_SAMPLE_ADDR would be set by 
> > the value of the SDAR register, which wouldn't be correct for 
> > the case of a page fault.
> 
> No, the PERF_SAMPLE_ADDR value only comes from SDAR for a hardware 
> counter overflow event.  For the page-fault software counter the 
> PERF_SAMPLE_ADDR value will always be the faulting address.

Corey, could you please add support for it in 'perf'? We dont want 
such sw-counter features to be in the kernel code without matching 
support in tools/perf/.

While user data symbols wont be resolved, if we have a 
--target-address switch in perf record we could see the faulting 
frequency (and the fault coverage - and ordering as well) of shared 
libraries, in perf report and perf annotate.

This would be a very useful facility.

Thanks,

	Ingo

  reply	other threads:[~2009-06-13 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  1:25 perf_counters: page fault trace record Corey Ashford
2009-06-13  3:43 ` Paul Mackerras
2009-06-13  7:04   ` Ingo Molnar
2009-06-13  8:44   ` Corey Ashford
2009-06-13  9:17     ` Paul Mackerras
2009-06-13 10:09       ` Ingo Molnar [this message]
2009-06-15 20:38         ` Corey Ashford

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=20090613100916.GA9959@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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