From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnaldo Carvalho de Melo Subject: Re: Getting PEBS to work Date: Mon, 23 May 2016 11:05:39 -0300 Message-ID: <20160523140539.GF8897@kernel.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail.kernel.org ([198.145.29.136]:57833 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752335AbcEWOFn (ORCPT ); Mon, 23 May 2016 10:05:43 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Brendan Gregg , Peter Zijlstra Cc: Vince Weaver , jim mauro , "linux-perf-use." Em Thu, May 19, 2016 at 06:06:36PM -0700, Brendan Gregg escreveu: > On Thu, May 19, 2016 at 5:47 PM, Vince Weaver wrote: > > On Thu, 19 May 2016, Brendan Gregg wrote: > >> On Thu, May 19, 2016 at 5:09 PM, jim mauro 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...