early_enable_events(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– early_enable_events(9) πŸ’–

okay bestie, this is the Kernel API Manual page for early_enable_events, and it's literally about enabling events from the bootup buffer. let's get into it πŸ’…


🌸 NAME 🌸

early_enable_events β€” enable events from the bootup buffer ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

void early_enable_events (struct trace_array *tr , char *buf , bool
       disable_first );

πŸŽ€ ARGUMENTS πŸŽ€

  • tr β€” the trace array to enable the events in πŸ’–
  • buf β€” the buffer containing the comma separated list of events ✨
  • disable_first β€” if true, disable all events in buf before enabling them πŸ‘‘

πŸ’… DESCRIPTION πŸ’…

so this function enables events from the bootup buffer. if disable_first is true, it will first disable all events in the buffer before enabling them. periodt πŸ’–

now for syscall events, which rely on a global refcount to register the SYSCALL_WORK_SYSCALL_TRACEPOINT flag (especially for pid 1), we must ensure the refcount hits zero before re-enabling them. a simple β€œdisable then enable” per-event is not enough if multiple syscalls are used, as the refcount will stay above zero. thus, we need a two-phase approach: disable all, then enable all πŸ”₯

literally the whole point, bestie: two phases, no shortcuts 🫢

🌈 SEE ALSO 🌈


mwah πŸ’‹ β€” source: ./kernel/trace Β· version: early_enable_events(9) Β· date: October 2026

πŸ“¦ where this page comes from