On Mon, 15 Sep 2025 18:19:53 -0700 Kalesh Singh kaleshsingh@google.com wrote:
Hi Steve,
Thanks for the comments and suggestion you are right we can use bpf to get the comm. There is nothing special about this trace event. I will drop comm in the next revision.
The reason I did the task_struct parameter (current): I believe there is a limitation that we must specify at least 1 parameter to the TRACE_EVENT() PROTO and ARGS macros.
OK, then this is another issue. We don't want tracepoint "markers". Each tracepoint can take up to 5K in memory due to the code it generates and the meta data to control it.
For something like that, we highly recommend dynamic probes (fprobes, kprobes, etc).
The only purpose of a static tracepoint is to get data within a function that is too difficult to get via a probe. It should never be used as a trigger where its purpose is "we hit this path".
-- Steve