Re: [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

From: Peter Zijlstra
Date: Fri Feb 11 2022 - 05:40:39 EST

Next message: Mike Rapoport: "Re: [PATCH 24/49] mm/vmstat: replace cpumask_weight with cpumask_empty where appropriate"
Previous message: Eugen.Hristev: "Re: [PATCH v4 07/11] media: atmel: atmel-isc: change format propagation to subdev into only verification"
In reply to: Namhyung Kim: "Re: [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Feb 10, 2022 at 09:55:27PM -0800, Namhyung Kim wrote:

> So you are ok with adding two new tracepoints, even if they are
> similar to what we already have in lockdep/lock_stat, right?

Yeah, I don't think adding tracepoints to the slowpaths of the various
locks should be a problem.

Next message: Mike Rapoport: "Re: [PATCH 24/49] mm/vmstat: replace cpumask_weight with cpumask_empty where appropriate"
Previous message: Eugen.Hristev: "Re: [PATCH v4 07/11] media: atmel: atmel-isc: change format propagation to subdev into only verification"
In reply to: Namhyung Kim: "Re: [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]