From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Michael Petlan <mpetlan@redhat.com>
Subject: [RFC] perf/x86/intel/uncore: pmu->type->single_fixed question
Date: Wed, 30 Nov 2016 11:51:05 +0100 [thread overview]
Message-ID: <20161130105105.GA25720@krava> (raw)
hi,
I'm trying to find out some documentation background for this part of uncore code:
---
static int uncore_pmu_event_init(struct perf_event *event)
{
...
if (event->attr.config == UNCORE_FIXED_EVENT) {
/* no fixed counter */
if (!pmu->type->fixed_ctl)
return -EINVAL;
/*
* if there is only one fixed counter, only the first pmu
* can access the fixed counter
*/
if (pmu->type->single_fixed && pmu->pmu_idx > 0)
return -EINVAL;
...
---
that for some uncore types (those with pmu->type->single_fixed) only
the first pmu (code_id == 0) will allow to touch the clocktick event
other cores boxes will not allow to open clocktick event, eventhough
it's announced via /sys/../events/..
I'm probably missing some HW logic of specific boxes that would explain
that, but I can't find it.
thanks for info,
jirka
next reply other threads:[~2016-11-30 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 10:51 Jiri Olsa [this message]
2016-11-30 14:45 ` [RFC] perf/x86/intel/uncore: pmu->type->single_fixed question Liang, Kan
2016-11-30 17:52 ` Andi Kleen
2016-12-01 16:34 ` Liang, Kan
2016-12-01 16:37 ` Peter Zijlstra
2016-12-12 14:49 ` Liang, Kan
2016-12-14 11:33 ` Jiri Olsa
2016-12-20 18:05 ` Liang, Kan
2017-01-16 13:15 ` Liang, Kan
2016-11-30 15:27 ` Liang, Kan
2016-11-30 15:38 ` Jiri Olsa
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=20161130105105.GA25720@krava \
--to=jolsa@redhat.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=peterz@infradead.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