[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a7fc5ab-682d-4fac-a547-9e4b1263dba7-agordeev@linux.ibm.com>
Date: Tue, 5 Aug 2025 16:14:39 +0200
From: Alexander Gordeev <agordeev@...ux.ibm.com>
To: Ilya Leoshkevich <iii@...ux.ibm.com>,
Thomas Richter <tmricht@...ux.ibm.com>
Cc: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>, Ian Rogers <irogers@...gle.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>, bpf@...r.kernel.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, Jiri Olsa <jolsa@...nel.org>,
Heiko Carstens <hca@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>
Subject: Re: [PATCH v3 2/2] perf bpf-filter: Enable events manually
On Tue, Aug 05, 2025 at 02:54:05PM +0200, Ilya Leoshkevich wrote:
Hi Thomas,
The below comments date to the initial version, so the question is
rather to you:
> On linux-next
This line is extra.
> commit b4c658d4d63d61 ("perf target: Remove uid from target")
> introduces a regression on s390. In fact the regression exists
> on all platforms when the event supports auxiliary data gathering.
So which commit it actually fixes: the above, the below or the both?
> Fixes: 63f2f5ee856ba ("libbpf: add ability to attach/detach BPF program to perf event")
Thanks!
Powered by blists - more mailing lists