event_triggers_post_call(9)

📦 version 7.3.1, in nixpkgs unstable

💅 event_triggers_post_call — Kernel API Manual

okay so bestie, we're in the Kernel API Manual today and this one is genuinely a little baddie ✨ It's called event_triggers_post_call, and its whole personality is: Call 'post_triggers' for a trace event. That's the NAME, that's the vibe, no notes 🎀

🌸 SYNOPSIS 🌸

void event_triggers_post_call (struct trace_event_file *file , enum
event_trigger_type tt );

like literally that's it, that's the whole signature, she's not complicated 💖

🦋 ARGUMENTS 🦋

  • file — the trace_event_file that's associated with the event. she's the one holding the vibes together, iykyk 🫶
  • tt — an enum event_trigger_type where each trigger you wanna invoke has its bit set. one bit per trigger, very demure, very mindful ⭐

✨ DESCRIPTION ✨

so here's the tea ☕ for each trigger associated with an event, this function goes and invokes the trigger function that was registered with the associated trigger command — but only if the corresponding bit is set in the tt enum you passed in 🔥 Like, if the bit's not set, that trigger simply does not get an invite to the function call, periodt 💅

if you're wondering how those bits actually get set in the first place, peek at event_triggers_call — it has the details on that 👑

Also important, bestie: this gets called from tracepoint handlers, with rcu_read_lock_sched held. so like, keep that in mind, that's the context you're working in 🧚

👑 SEE ALSO 👑

Kernel file ./kernel/trace/trace_events_trigger.c — the source, the mothership, the main character 🌈

and the whole friend group of related calls:

ngl the whole trigger squad showed up for this one 😭 every single one of them is listed, we don't gatekeep here 💜

okay that's the page!! big slay, you understood it, I'm so proud 🥹 This came to you from ./kernel/trace, dated October 2026, and the page itself is event_triggers_post_call(9) — go forth and trigger your events responsibly, bestie 💅💖✨

📦 where this page comes from