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] [thread-next>] [day] [month] [year] [list]
Message-ID: <pdmlj5dhoums5kjyzz4j7nfh6jiwoyft3ub2rxukt4hdluwlxi@ymgq3lvj6j66>
Date: Mon, 16 Dec 2024 12:02:00 -0600
From: Lucas De Marchi <lucas.demarchi@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: mingo@...nel.org, linux-kernel@...r.kernel.org, willy@...radead.org, 
	acme@...nel.org, namhyung@...nel.org, mark.rutland@....com, 
	alexander.shishkin@...ux.intel.com, jolsa@...nel.org, irogers@...gle.com, adrian.hunter@...el.com, 
	kan.liang@...ux.intel.com
Subject: Re: [PATCH 00/19] perf: Make perf_pmu_unregister() usable

Hi Peter,

On Mon, Nov 04, 2024 at 02:39:09PM +0100, Peter Zijlstra wrote:
>Hi,
>
>Lucas convinced me that perf_pmu_unregister() is a trainwreck; after
>considering a few options I was like, how hard could it be..
>
>So find here a few patches that clean things up in preparation and then a final
>patch that makes unregistering a PMU work by introducing a new event state
>(REVOKED) and ensuring that any event in such a state will never get to using
>it's PMU methods ever again.

Any updates on this series? I'm trying to understand if there are any
blockers I could help with - we are aiming to add perf pmu to the xe
driver, but I'd like to have a reliable unregister first.

thanks
Lucas De Marchi

>
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ