[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1dc554eb-7ed2-45b3-109f-8cec286b4525@arm.com>
Date: Tue, 2 Oct 2018 17:19:03 +0100
From: Jean-Philippe Brucker <jean-philippe.brucker@....com>
To: Shameer Kolothum <shameerali.kolothum.thodi@...wei.com>,
lorenzo.pieralisi@....com, robin.murphy@....com
Cc: mark.rutland@....com, vkilari@...eaurora.org,
neil.m.leeder@...il.com, pabba@...eaurora.org,
john.garry@...wei.com, will.deacon@....com,
rruigrok@...eaurora.org, linuxarm@...wei.com,
linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
guohanjun@...wei.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/3] perf: add arm64 smmuv3 pmu driver
On 02/10/2018 15:11, Jean-Philippe Brucker wrote:
>> + cfgr = readl_relaxed(smmu_pmu->reg_base + SMMU_PMCG_CFGR);
Something I missed previously: when SMMU_PMCG_CFGR.SID_FILTER_TYPE is 1,
filtering for all counters is configured by SMMU_PMCG_SMR0 and
SMMU_PMCG_EVTYPER0 (instead of having one separate filter per counter).
In that mode with your patch, if the user applies a filter to the first
event in the list passed to perf, it will be applied to all events.
Filter applied on any subsequent event will be ignored. Could we make
this more explicit? Maybe in the probe print that the PMCG is
global-filtering, and when attempting to apply a filter to something
else than EVCNTR0, return an error?
Thanks,
Jean
Powered by blists - more mailing lists