event_trace_add_tracer(9)

💫 event_trace_add_tracer(9) 💫

okay so bestie, this is a page from the Kernel API Manual and it's literally about giving a brand-new trace instance its own little events corner in the filesystem ✨ buckle up 🎀

---

🌸 NAME 🌸

event_trace_add_tracer — adds an instance of a trace_array to events 🦋

---

✨ SYNOPSIS ✨

int event_trace_add_tracer (struct dentry *parent , struct trace_array *tr );

---

💅 ARGUMENTS 💅

• parent — the parent dentry, aka where the files/directories for events are gonna live 🏠
• tr — the trace array that's associated with these events 👑

---

🫶 DESCRIPTION 🫶

so when a new instance gets created, it lowkey needs to set up its own events directory, plus all the other files that go with events. this function handles that, and it also creates the event hierarchy inside the parent/events directory 🌈

returns 0 on success. periodt 💯

⚠️ ngl this one's serious: it must be called with event_mutex held. no cap, don't skip that 🔒

---

🔥 SEE ALSO 🔥

Kernel file ./kernel/trace/trace_events.c, plus all these icons 👑:

• trace_event_buffer_reserve(9)
• trace_set_clr_event(9)
• trace_array_set_clr_event(9)
• t_show_filters(9)
• t_show_triggers(9)
• ftrace_event_show_filters_open(9)
• ftrace_event_show_triggers_open(9)
• trace_get_event_file(9)
• trace_put_event_file(9)
• early_enable_events(9)

---

and that's the whole vibe bestie 💖 this cutie lives in ./kernel/trace, it's the October 2026 edition, and the page is literally called event_trace_add_tracer(9) — slay, go read the source, mwah 🧚💜