On Thu, Jun 19, 2025 at 04:56:59AM -0400, Steven Rostedt wrote: > We have a many to many relationship here where a task_work doesn't work. > > That is, you can have a tracer that expects callbacks from several > tasks at the same time, as well as some of those tasks expect to send a > callback to different tracers. > > Later patches add a bitmask to every task that gets set to know which > trace to use. > > Since the number of tracers that can be called back is fixed to the > number of bits in long (for the bitmask), I can get rid of the link > list and make it into an array. That would make this easier. So something sketching this design decision might be useful. Perhaps a comment in the file itself? I feel much of this complication stems from the fact you're wanting to make this perhaps too generic.
