Re: [PATCH v3 01/11] io_uring: Use trace_call__##name() at guarded tracepoint call sites

[Jens Axboe <axboe@kernel.dk>]

On 5/15/26 8:04 AM, Steven Rostedt wrote:
> On Fri, 15 May 2026 09:59:03 -0400
> "Vineeth Pillai (Google)" <vineeth@bitbyteword.org> wrote:
> 
>> From: Vineeth Pillai <vineeth@bitbyteword.org>
>>
> 
> Hi Vineeth,
> 
>> Replace trace_foo() with the new trace_call__foo() at sites already
>> guarded by trace_foo_enabled(), avoiding a redundant
>> static_branch_unlikely() re-evaluation inside the tracepoint.
>> trace_call__foo() calls the tracepoint callbacks directly without
>> utilizing the static branch again.
>>
> 
>> Original v2 series:
>> https://lore.kernel.org/linux-trace-kernel/20260323160052.17528-1-vineeth@bitbyteword.org/
>>
>> Parts of the original v2 series have already been merged in mainline.
>> This patch is being reposted as a follow-up cleanup for the remaining
>> unmerged pieces.
> 
> This part should go below the '---'. There's no reason to add it to the git
> change log.

I pruned it.

> You should probably also state that these can now go in individually as all
> the dependencies are upstream.

I think he did, at least that's how I read it.


-- 
Jens Axboe