linux-kernel - Re: [PATCH v2] perf arch events: Fix duplicate RISC-V SBI firmware event name

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: <CAP-5=fV3NXkKsCP1WH0_qLRNpL+WuP8S3h1=cHaUMH5MFkVHQg@mail.gmail.com>
Date: Thu, 1 Aug 2024 10:04:36 -0700
From: Ian Rogers <irogers@...gle.com>
To: acme@...nel.org, namhyung@...nel.org
Cc: Eric Lin <eric.lin@...ive.com>, peterz@...radead.org, mingo@...hat.com, 
	alexander.shishkin@...ux.intel.com, jolsa@...nel.org, palmer@...belt.com, 
	aou@...s.berkeley.edu, peterlin@...estech.com, dminus@...estech.com, 
	locus84@...estech.com, jisheng.teoh@...rfivetech.com, inochiama@...look.com, 
	n.shubin@...ro.com, linux-kernel@...r.kernel.org, samuel.holland@...ive.com, 
	patchwork-bot+linux-riscv@...nel.org, linux-riscv@...ts.infradead.org, 
	linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v2] perf arch events: Fix duplicate RISC-V SBI firmware
 event name

On Thu, Aug 1, 2024 at 9:40 AM <patchwork-bot+linux-riscv@...nel.org> wrote:
>
> Hello:
>
> This patch was applied to riscv/linux.git (fixes)
> by Palmer Dabbelt <palmer@...osinc.com>:
>
> On Fri, 19 Jul 2024 19:50:18 +0800 you wrote:
> > Currently, the RISC-V firmware JSON file has duplicate event name
> > "FW_SFENCE_VMA_RECEIVED". According to the RISC-V SBI PMU extension[1],
> > the event name should be "FW_SFENCE_VMA_ASID_SENT".
> >
> > Before this patch:
> > $ perf list
> >
> > [...]
>
> Here is the summary with links:
>   - [v2] perf arch events: Fix duplicate RISC-V SBI firmware event name
>     https://git.kernel.org/riscv/c/63ba5b0fb4f5
>
> You are awesome, thank you!

Fwiw, as this change is in tools/perf/pmu-events I was expecting it to
go through the perf-tools/perf-tools-next tree.

Thanks,
Ian