linux-kernel - Re: [PATCH] perf/arm-cmn: Reset DTM_PMU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <167415190277.3429004.658905197029681030.b4-ty@kernel.org>
Date:   Thu, 19 Jan 2023 19:08:43 +0000
From:   Will Deacon <will@...nel.org>
To:     mark.rutland@....com, Robin Murphy <robin.murphy@....com>
Cc:     catalin.marinas@....com, kernel-team@...roid.com,
        Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] perf/arm-cmn: Reset DTM_PMU_CONFIG at probe

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