All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Selva <manuel.selva@insa-lyon.fr>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Load latency sampling on Sandy Bridge
Date: Wed, 29 Oct 2014 20:21:57 +0100	[thread overview]
Message-ID: <54513E55.9060503@insa-lyon.fr> (raw)
In-Reply-To: <alpine.DEB.2.11.1410291509160.895@vincent-weaver-1.umelst.maine.edu>

Yes the problem is there ! Thanks I am not enough "fluent" in kernel 
code to identify this. Here is my dmesg:

perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode

Does it mean that I must "upgrade my hardware" through the upgrade of 
microcode ? I never did such a thing.

Manu

On 10/29/2014 08:12 PM, Vince Weaver wrote:
> On Wed, 29 Oct 2014, Manuel Selva wrote:
>
>> Yes, perf mem doesn't work on my Sandy Bridge. I should be missing something,
>> maybe a kernel parameter somewhere, or something like that, but I don't know
>> where searching ...
>
> well if you're getting operation not supported you are probably running
> into this chunk of code in arch/x86/kernel/cpu/perf_event.c
>
>
> int x86_pmu_hw_config(struct perf_event *event)
> {
>          if (event->attr.precise_ip) {
>                  int precise = 0;
>
>                  /* Support for constant skid */
>                  if (x86_pmu.pebs_active && !x86_pmu.pebs_broken) {
>                          precise++;
>
>                          /* Support for IP fixup */
>                          if (x86_pmu.lbr_nr || x86_pmu.intel_cap.pebs_format >= 2)
>                                  precise++;
>                  }
>
>                  if (event->attr.precise_ip > precise)
>                          return -EOPNOTSUPP;
>
>
>
> and if you look, pebs_broken can be enabled on Sandybridge CPUs due to
> firmware errata.  Did you check your dmesg for messages starting with
> PEBS?
>
> Vince
>

  reply	other threads:[~2014-10-29 19:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  8:07 Load latency sampling on Sandy Bridge Manuel Selva
2014-10-29 16:09 ` Vince Weaver
2014-10-29 17:05   ` Manuel Selva
2014-10-29 18:53     ` Vince Weaver
2014-10-29 18:50       ` Manuel Selva
2014-10-29 19:12         ` Vince Weaver
2014-10-29 19:21           ` Manuel Selva [this message]
2014-10-29 20:02             ` Vince Weaver
2014-10-29 20:15               ` Manuel Selva

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=54513E55.9060503@insa-lyon.fr \
    --to=manuel.selva@insa-lyon.fr \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=vincent.weaver@maine.edu \
    /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.