* [PATCH] perf/arm-cmn: Reset DTM_PMU_CONFIG at probe
@ 2022-12-05 19:46 Robin Murphy
2023-01-19 19:08 ` Will Deacon
0 siblings, 1 reply; 2+ messages in thread
From: Robin Murphy @ 2022-12-05 19:46 UTC (permalink / raw)
To: will, mark.rutland; +Cc: linux-arm-kernel, linux-kernel
Although we treat the DTM counters as free-running such that we're not
too concerned about the initial DTM state, it's possible for a previous
user to have left DTM counters enabled and paired with DTC counters.
Thus if the first events are scheduled using some, but not all, DTMs,
the as-yet-unused ones could end up adding spurious increments to the
event counts at the DTC. Make sure we sync our initial DTM_PMU_CONFIG
state to all the DTMs at probe time to avoid that possibility.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
---
drivers/perf/arm-cmn.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
index 0b2df72cee9f..81b0dfd511aa 100644
--- a/drivers/perf/arm-cmn.c
+++ b/drivers/perf/arm-cmn.c
@@ -1862,6 +1862,7 @@ static void arm_cmn_init_dtm(struct arm_cmn_dtm *dtm, struct arm_cmn_node *xp, i
dtm->base = xp->pmu_base + CMN_DTM_OFFSET(idx);
dtm->pmu_config_low = CMN_DTM_PMU_CONFIG_PMU_EN;
+ writeq_relaxed(dtm->pmu_config_low, dtm->base + CMN_DTM_PMU_CONFIG);
for (i = 0; i < 4; i++) {
dtm->wp_event[i] = -1;
writeq_relaxed(0, dtm->base + CMN_DTM_WPn_MASK(i));
--
2.36.1.dirty
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] perf/arm-cmn: Reset DTM_PMU_CONFIG at probe
2022-12-05 19:46 [PATCH] perf/arm-cmn: Reset DTM_PMU_CONFIG at probe Robin Murphy
@ 2023-01-19 19:08 ` Will Deacon
0 siblings, 0 replies; 2+ messages in thread
From: Will Deacon @ 2023-01-19 19:08 UTC (permalink / raw)
To: mark.rutland, Robin Murphy
Cc: catalin.marinas, kernel-team, Will Deacon, linux-kernel,
linux-arm-kernel
On Mon, 5 Dec 2022 19:46:13 +0000, Robin Murphy wrote:
> Although we treat the DTM counters as free-running such that we're not
> too concerned about the initial DTM state, it's possible for a previous
> user to have left DTM counters enabled and paired with DTC counters.
> Thus if the first events are scheduled using some, but not all, DTMs,
> the as-yet-unused ones could end up adding spurious increments to the
> event counts at the DTC. Make sure we sync our initial DTM_PMU_CONFIG
> state to all the DTMs at probe time to avoid that possibility.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] perf/arm-cmn: Reset DTM_PMU_CONFIG at probe
https://git.kernel.org/will/c/bb21ef19a3d8
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-01-19 19:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-05 19:46 [PATCH] perf/arm-cmn: Reset DTM_PMU_CONFIG at probe Robin Murphy
2023-01-19 19:08 ` Will Deacon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®