[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC023FC273@IRSMSX103.ger.corp.intel.com>
Date: Mon, 20 Jun 2016 10:26:30 +0000
From: "Odzioba, Lukasz" <lukasz.odzioba@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Liang, Kan" <kan.liang@...el.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"eranian@...gle.com" <eranian@...gle.com>,
"acme@...nel.org" <acme@...nel.org>,
"alexander.shishkin@...ux.intel.com"
<alexander.shishkin@...ux.intel.com>, "bp@...e.de" <bp@...e.de>,
"Anaczkowski, Lukasz" <lukasz.anaczkowski@...el.com>
Subject: RE: [PATCH 1/1] perf/x86/intel: Add extended event constraints for
Knights Landing
On 08.06.2016 Peter Zijlstra wrote:
> How does this work in the light of intel_alt_er() ?
Hi Peter,
If the constrained bit is valid on only one of the OCR MSRs (like in case of KNL),
then OCR valid mask will forbid altering it by the other MSR in intel_alt_er.
If constrained bit is valid on both OCR MSR, so it can be safely altered by
intel_alt_er, but in this case it should be defined twice - for each MSR i.e:
INTEL_EEVENT_CONSTRAINT(0x01b7, 0, 0x1); // bit0 can be used only on PMC0
INTEL_EEVENT_CONSTRAINT(0x02b7, 0, 0x1); // bit0 can be used only on PMC0
I hope that answers your question.
Thanks,
Lukas
Powered by blists - more mailing lists