Date: Wed, 30 Nov 2016 11:51:05 +0100
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
Message-ID: <20161130105105.GA25720@krava>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 996
Lines: 31

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