From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Brendan Gregg <brendan.d.gregg@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
jim mauro <jim.mauro@gmail.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: Getting PEBS to work
Date: Mon, 23 May 2016 11:05:39 -0300 [thread overview]
Message-ID: <20160523140539.GF8897@kernel.org> (raw)
In-Reply-To: <CAE40pddwJZOikG2kS9z7pwhPgvBsupKsskangpX2FZriQ3ERmQ@mail.gmail.com>
Em Thu, May 19, 2016 at 06:06:36PM -0700, Brendan Gregg escreveu:
> On Thu, May 19, 2016 at 5:47 PM, Vince Weaver <vincent.weaver@maine.edu> wrote:
> > On Thu, 19 May 2016, Brendan Gregg wrote:
> >> On Thu, May 19, 2016 at 5:09 PM, jim mauro <jim.mauro@gmail.com> wrote:
> >> Nor did r01c0. But pretty interesting you got PEBS output, and on
> >> Linux 3.8. So maybe my 3.13 isn't the problem...
> > does your dmesg say anything? If I recall there are sandybridge machines
> > with PEBS disabled due to errata. Usually you need to update your
> > CPU firmware to get it working.
>
> # dmesg | egrep -i 'pmu|pmc|pebs'
> [ 0.381095] Performance Events: PEBS fmt1+, 16-deep LBR,
> SandyBridge events, full-width counters, Intel PMU driver.
> [ 0.381101] perf_event_intel: PEBS disabled due to CPU errata,
> please upgrade microcode
> [ 0.395348] NMI watchdog: enabled on all CPUs, permanently consumes
> one hw-PMU counter.
> [ 1.231836] nouveau [ PMC][0000:01:00.0] MSI interrupts enabled
>
> Gah, it was there all along!
Wish this was exported by the kernel somehow, then tooling could emit a
sensible message :-\
- Arnaldo
> Thanks Vince. I hope future PEBS explorers find the commands in this
> thread useful!
>
> Now I have to update some microcode...
next prev parent reply other threads:[~2016-05-23 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 22:29 Getting PEBS to work Brendan Gregg
[not found] ` <CAPAnC4PsdkN=9NQ6D_n2p6NX64yB0ASXhTqQRsGw5N3Jvr3d2A@mail.gmail.com>
2016-05-19 23:13 ` Brendan Gregg
[not found] ` <CAPAnC4PGktN_QYu9T6f5=p0cJ1wV59TWNcPYpskYDck=O=7faw@mail.gmail.com>
2016-05-20 0:09 ` Brendan Gregg
[not found] ` <CAPAnC4NObR7Fe-fZr9z5tdD0cyyVhd6WojN-aWst2Z2rtxQ6SQ@mail.gmail.com>
2016-05-20 0:19 ` Brendan Gregg
2016-05-20 0:47 ` Vince Weaver
2016-05-20 1:06 ` Brendan Gregg
2016-05-23 14:05 ` Arnaldo Carvalho de Melo [this message]
2016-05-24 10:17 ` Peter Zijlstra
2016-05-24 12:19 ` Arnaldo Carvalho de Melo
2016-05-24 14:02 ` Andi Kleen
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=20160523140539.GF8897@kernel.org \
--to=acme@kernel.org \
--cc=brendan.d.gregg@gmail.com \
--cc=jim.mauro@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=peterz@infradead.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).