unpause_named_trigger(9)
π unpause_named_trigger(9) π
okay bestie, welcome to the Kernel API Manual β we're talking about one very specific little function today, and honestly it's giving "team player" energy. π«Ά
πΈ NAME πΈ
unpause_named_trigger β Un-pause all named triggers with the same name π
β¨ SYNOPSIS β¨
void unpause_named_trigger (struct event_trigger_data *data );
π ARGUMENTS π
dataβ the trigger data of a named trigger that you want to unpause. that's the one you're handing over so it can do its thing β¨
π¦ DESCRIPTION π¦
so here's the vibe: unpause_named_trigger un-pauses a named trigger along with all other triggers having the same name. not just the one, not a little subset β all of them with that name, periodt. π
and why? because named triggers share a common set of data. so unpausing only one is literally meaningless β there's no solo unpause era here. unpausing one named trigger needs to unpause all triggers with the same name. that's the whole point, no cap. π¦
π SEE ALSO π
Kernel file ./kernel/trace/trace_events_trigger.c π
event_triggers_call(9)event_triggers_post_call(9)event_trigger_count(9)event_trigger_print(9)event_trigger_init(9)event_trigger_free(9)clear_event_triggers(9)update_cond_flag(9)register_trigger(9)unregister_trigger(9)event_trigger_check_remove(9)event_trigger_empty_param(9)event_trigger_separate_filter(9)trigger_data_alloc(9)event_trigger_parse_num(9)event_trigger_set_filter(9)event_trigger_reset_filter(9)event_trigger_register(9)event_trigger_unregister(9)event_trigger_parse(9)set_trigger_filter(9)find_named_trigger(9)is_named_trigger(9)save_named_trigger(9)del_named_trigger(9)pause_named_trigger(9)set_named_trigger_data(9)
mwah π this page lives in ./kernel/trace and it's dated October 2026 β catch you in the next manpage, bestie πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms