public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Ashford <cjashfor@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>
Subject: perf_counter: question about the user page data_head field
Date: Mon, 04 May 2009 14:56:04 -0700	[thread overview]
Message-ID: <49FF6474.7090000@linux.vnet.ibm.com> (raw)

Hi,

In working on the PAPI substrate using the "Performance Counters for 
Linux" implementation (code that's currently in linux-2.6-tip, commit: 
c786fa3dc42e8e898cf1a33f9f5a25b61c7043f5), I encountered an issue with 
the data_head field.

I am implementing the profiling part of the substrate, and am using the 
mmap'd data pages to capture IP samples.  This is working quite well, 
and I've been able to profile on multiple events simultaneously.

However, one thing I ran into is when my code examines the data_head 
field from user space, it's always a multiple of the page size.  So it's 
apparently updated only on mmap page overflow.  I think I understand 
that this is done for efficiency reasons, but it's a limitation for the 
user space app in that they can miss up to 255 records (4096 byte pages 
/ 16-byte records), because the following mmap page is non empty but not 
full.

Perhaps I'm missing something.  Is there a way to force data_head to be 
updated from user space?  If not, I'd like to request that a new 
mechanism for doing such, perhaps via an ioctl call.

Thanks for your consideration,

- Corey

Corey Ashford
Software Engineer
IBM Linux Technology Center, Linux Toolchain
Beaverton, OR
503-578-3507
cjashfor@us.ibm.com


                 reply	other threads:[~2009-05-04 21:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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