linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: linux-perf-users@vger.kernel.org
Subject: Re: PEBS availability
Date: Fri, 27 May 2011 11:13:25 +0100	[thread overview]
Message-ID: <4DDF7945.5@draigBrady.com> (raw)
In-Reply-To: <20110524203751.GA31843@dev1756.snc6.facebook.com>

On 24/05/11 21:37, Arun Sharma wrote:
> On Tue, May 24, 2011 at 04:49:27PM +0100, Pádraig Brady wrote:
>>
>> So am I out of look with my new i3 sandy bridge CPU?
>> Are PEBS restricted to i7 versions only?
>> Is this documented anywhere?
> 
> i3 and i7 are marketing terms that don't mean much.
> Engineers care more about the output of:
> 
> #!/usr/bin/env python
> 
> import struct
> 
> def cpuid(eax):
>     f = open("/dev/cpu/0/cpuid", "rb")
>     f.seek(eax)
>     data = f.read(16)
>     f.close()
>     return struct.unpack('IIII', data)
> 
> print "%x" % cpuid(1)[0]
> 
>>
>> Maybe I need some kernel support as hinted at by:
>> http://lwn.net/Articles/430100/
>> My kernel is 2.6.38.6-27.fc15.x86_64
> 
> Your kernel probably has support for most of PEBS. What's missing is
> support in user space for all the events in manuals.
> 
> http://thread.gmane.org/gmane.comp.linux.perfmon2.devel/2912

Well that was easy.
My Fedora 15 kernel was missing support for sandy bridge PEBS,
and creating a new bzImage with the patch I referenced makes
the counters available:

old-kern:$ perf stat -e L1-dcache-loads true
  Error: L1-dcache-loads event is not supported.
  Fatal: Not all events could be opened.

new-kern:$ perf stat -e L1-dcache-loads true
  98,331 L1-dcache-loads

cheers,
Pádraig.

      parent reply	other threads:[~2011-05-27 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 15:49 PEBS availability Pádraig Brady
2011-05-24 17:26 ` David Ahern
2011-05-24 20:37 ` Arun Sharma
2011-05-25  8:33   ` Pádraig Brady
2011-05-27 10:13   ` Pádraig Brady [this message]

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=4DDF7945.5@draigBrady.com \
    --to=p@draigbrady.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).