All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Arun Sharma <asharma@fb.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: PEBS availability
Date: Wed, 25 May 2011 09:33:51 +0100	[thread overview]
Message-ID: <4DDCBEEF.4000607@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]

206a7

>> 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
> 
> Kernel is still missing:
> 
> * Ability to dump all of x86 architectural state to perf.data on an
>   event
> * Uncore events
> * Exposing offcore events to userspace
> 
> http://lwn.net/Articles/441209/ has a summary of recent discussions on
> this topic.

Excellent. I'll start digging from there.

cheers,
Pádraig.

  reply	other threads:[~2011-05-25  8:35 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 [this message]
2011-05-27 10:13   ` Pádraig Brady

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=4DDCBEEF.4000607@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=asharma@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.