From: Peter Zijlstra <peterz@infradead.org>
To: Mike Hommey <mh@glandium.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with perf hardware counters grouping
Date: Thu, 01 Sep 2011 13:53:32 +0200 [thread overview]
Message-ID: <1314878012.11566.7.camel@twins> (raw)
In-Reply-To: <20110831085718.GB13884@glandium.org>
On Wed, 2011-08-31 at 10:57 +0200, Mike Hommey wrote:
> I'm having two different problems with perf hardware counters with a
> group leader:
> - perf_event_open()ing more than 3 makes all of them always return a
> value of 0;
> - perf_event_open()ing more than 4 fails with ENOSPC.
I'm guessing you're running on something x86, either AMD-Fam10-12 or
Intel-NHM+.
Both those have 4 generic hardware counters, but x86 defaults to
enabling the NMI watchdog which takes one, leaving you with 3 (try: echo
0 > /proc/sys/kernel/nmi_watchdog). If you had looked at your dmesg
output you'd have found lines like:
NMI watchdog enabled, takes one hw-pmu counter.
The code can only check if the group as a whole could possibly fit on a
PMU, which is where your failure on >4 comes from.
What happens with your >3 case is that while the group is valid and
could fit on the PMU, it won't fit at runtime because the NMI watchdog
is taking one and won't budge (cpu-pinned counter have precedence over
any other kind), effectively starving your group of pmu runtime.
Also, we should fix that return to say -EINVAL or so.
next prev parent reply other threads:[~2011-09-01 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 8:57 Problem with perf hardware counters grouping Mike Hommey
2011-09-01 11:53 ` Peter Zijlstra [this message]
2011-09-01 11:59 ` Mike Hommey
2011-09-01 12:40 ` Peter Zijlstra
2011-09-01 15:21 ` Vince Weaver
2011-09-01 16:41 ` Peter Zijlstra
2011-09-01 17:16 ` Vince Weaver
2011-09-01 17:24 ` Vince Weaver
2011-09-06 19:43 ` Vince Weaver
2011-09-06 20:22 ` Don Zickus
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=1314878012.11566.7.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh@glandium.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 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).