linux-kernel - Re: [PATCH] perf vendor events amd: Fix Zen 4 cache latency events

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: <170957856863.1606352.5043156720799964711.b4-ty@kernel.org>
Date: Mon,  4 Mar 2024 10:56:44 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: linux-kernel@...r.kernel.org,
	linux-perf-users@...r.kernel.org,
	Sandipan Das <sandipan.das@....com>
Cc: eranian@...gle.com,
	jolsa@...nel.org,
	ananth.narayan@....com,
	acme@...nel.org,
	peterz@...radead.org,
	irogers@...gle.com,
	alexander.shishkin@...ux.intel.com,
	adrian.hunter@...el.com,
	ravi.bangoria@....com,
	mark.rutland@....com,
	mingo@...hat.com
Subject: Re: [PATCH] perf vendor events amd: Fix Zen 4 cache latency events

On Fri, 1 Mar 2024 14:14:31 +0530, Sandipan Das wrote:
> L3PMCx0AC and L3PMCx0AD, used in l3_xi_sampled_latency* events, have a
> quirk that requires them to be programmed with SliceId set to 0x3.
> Without this, the events do not count at all and affects dependent
> metrics such as l3_read_miss_latency.
> 
> If ThreadMask is not specified, the amd-uncore driver internally sets
> ThreadMask to 0x3, EnAllCores to 0x1 and EnAllSlices to 0x1 but does
> not set SliceId. Since SliceId must also be set to 0x3 in this case,
> specify all the other fields explicitly.
> 
> [...]

Applied to perf-tools-next, thanks!

Best regards,
-- 
Namhyung Kim <namhyung@...nel.org>