register_trace_event(9)

💖 register_trace_event(9) — Kernel API Manual 💖

okay bestie, gather round, because we're about to make your event type known to the kernel. this is the glow-up registration moment. ✨

✨ NAME ✨

register_trace_event — register output for an event type

like, you made an event type, and now you're telling the tracing system "hey, she's with me." 🫶

🌸 SYNOPSIS 🌸

int register_trace_event (struct trace_event *event );

🎀 ARGUMENTS 🎀

• event — the event type to register. that's it, that's the whole vibe. she's the one going on the list. 💅

🦋 DESCRIPTION 🦋

so here's the tea: event types are stored in a hash, and that hash is literally what the kernel digs through to find a way to print an event. it's giving "filing system but make it cute." 🗂️

if event->type is set, bestie, it will use that type. no notes, respect the choice. but if you didn't set it, no worries — it will assign a type to use for you. so generous.

⚠️ lowkey important: if you assign your own type, please make sure it is added to the trace_type enum in trace.h, to avoid collisions with the dynamic types. fr fr, don't skip this step or you'll have two events fighting for the same number and it's gonna be a whole mess. 💀

Returns the event type number, or zero on error. that zero is the "nope" answer, so vibe check your return value, okay? 😭

👑 SEE ALSO 👑

Kernel file ./kernel/trace/trace_output.c

• trace_print_bitmask_seq(9)
• trace_print_hex_seq(9)
• trace_print_lat_fmt(9)
• ftrace_find_event(9)
• unregister_trace_event(9)

---

🎀 that's the whole page bestie — slay, go register that event 🎀

and for the receipts: this one lives under the ./kernel/trace source, dated October 2026, in the Kernel API Manual — register_trace_event(9), icon behavior only. 💖🌈⭐