linux-perf-users.vger.kernel.org archive mirror
 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 21:15:30 +0100	[thread overview]
Message-ID: <54514AE2.9010702@insa-lyon.fr> (raw)
In-Reply-To: <alpine.DEB.2.11.1410291601080.895@vincent-weaver-1.umelst.maine.edu>

many thanks, it works !!!

On ubuntu: sudo apt-get install intel-microcode

-----
Manu

On 10/29/2014 09:02 PM, Vince Weaver wrote:
> On Wed, 29 Oct 2014, Manuel Selva wrote:
>
>> 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.
>
> Usually the microcode is updated at boot time.  Usually your distribution
> will have some sort of microcode update package you can install that will
> do this for you automatically.
>
> Vince
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>

      reply	other threads:[~2014-10-29 20:15 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
2014-10-29 20:02             ` Vince Weaver
2014-10-29 20:15               ` Manuel Selva [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=54514AE2.9010702@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 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).