tracer_tracing_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– tracer_tracing_enable(9) πŸ’–

okay so bestie, this is a page from the Kernel API Manual and honestly it's a short one but it's lowkey iconic β€” welcome to tracer_tracing_enable ✨


🌸 NAME 🌸

tracer_tracing_enable β€” the counter part of tracer_tracing_disable() 🫢

like, the other half. the remix. the sequel. the "we're so back" of the pair πŸ’…


⭐ SYNOPSIS ⭐

void tracer_tracing_enable (struct trace_array *tr );

no cap, that's the whole signature. void in, void out, struct trace_array *tr in the middle, slay πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • tr β€” the trace array that had tracer_tracincg_disable called on it πŸ‘€
yes bestie, that spelling is exactly how it's written on the page β€” tracer_tracincg_disable, not tracer_tracing_disable. we are reproducing it character for character because we do not edit the source material πŸ’€

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe check: you call this after tracer_tracing_disable has already been called on tr, at the point where it's safe to re-enable tracing 🌈

that's it. that's the whole thing. it's the "okay we're done being careful, turn the lights back on" function ✨ and the page is very clear about the ordering β€” after the disable, when it's safe. not before, not whenever, not vibes-based. periodt πŸ‘‘


πŸ’œ SEE ALSO πŸ’œ

the whole friend group, fr fr β€” plus the kernel file they all live in:

Kernel file ./kernel/trace/trace.c

go read them all, iykyk πŸ“šπŸ’–


🧚 quick reminder: this page is tracer_tracing_enable(9) from the Kernel API Manual β€” the file lives under ./kernel/trace and this particular printing is dated October 2026. screenshot it, cite it, cite it properly bestie πŸŽ€πŸ’…
πŸ“¦ where this page comes from