ftrace_ops_s...lobal_filter(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ftrace_ops_set_global_filter β€” a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for ftrace_ops_set_global_filter. yes that's the whole title, yes the header got squished in the middle (the manpage listed it as ftrace_ops_s...lobal_filter(9), iconic abbreviation behaviour honestly πŸŽ€). this is the one you call when you want your ftrace ops to play nice with the global filters. it's giving "let the whole trace share one vibe check" ✨


🌸 SYNOPSIS 🌸

void ftrace_ops_set_global_filter (struct ftrace_ops *ops );

that's it. one function, one argument, returns void, no drama πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ops β€” the ops which will use the global filters. like, these specific ops. the ones you're handing over. no cap 🫢

πŸ’– DESCRIPTION πŸ’–

so here's the tea β˜• β€” ftrace users who need global function trace filtering should call this. that's the whole assignment, fr fr.

it can set the global filter only if ops were not initialized before. so if your ops already went through init? yeah, this isn't gonna work for you, bestie 😭 the order of operations matters, always does.

⚠️ heads up: the "only if not initialized before" bit is a real constraint, not a vibe. don't come crying to me when you init first and then try to set the global filter πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

all the siblings in the family, kept in their exact original order because we don't do chaos here πŸ‘‘

ftrace_lookup_ip(9), ftrace_free_filter(9), ftrace_hash_move(9), ftrace_location_range(9), ftrace_location(9), ftrace_text_reserved(9), ftrace_bug(9), ftrace_update_record(9), ftrace_test_record(9), ftrace_get_addr_new(9), ftrace_get_addr_curr(9), ftrace_rec_iter_start(9), ftrace_rec_iter_next(9), ftrace_rec_iter_record(9), ftrace_run_stop_machine(9), arch_ftrace_update_code(9), ftrace_startup_subops(9), ftrace_shutdown_subops(9), ftrace_regex_open(9), allocate_ftrace_func_mapper(9), ftrace_func_mapper_find_ip(9), ftrace_func_mapper_add_ip(9), ftrace_func_mapper_remove_ip(9), free_ftrace_func_mapper(9), register_ftrace_direct(9), unregister_ftrace_direct(9), modify_ftrace_direct_nolock(9), modify_ftrace_direct(9), hash_add(9), update_ftrace_direct_add(9), hash_sub(9), update_ftrace_direct_del(9), update_ftrace_direct_mod(9), ftrace_set_filter_ip(9), ftrace_set_filter_ips(9), ftrace_set_filter(9), ftrace_set_notrace(9), ftrace_set_global_filter(9), ftrace_set_global_notrace(9), ftrace_ops_get_func(9), ftrace_kill(9), ftrace_is_dead(9), register_ftrace_function(9), unregister_ftrace_function(9), ftrace_lookup_symbols(9)

and where does this page even live? πŸ‘€ right here:

  • Kernel file: ./kernel/trace/ftrace.c

okay that's the whole page!! go forth and set those global filters correctly, bestie πŸ§šπŸ’œ

signed off with love from the ./kernel/trace directory, dated October 2026, and yeah β€” the footer still says ftrace_ops_s...lobal_filter(9) because we keep the original names around here πŸ’…βœ¨

πŸ“¦ where this page comes from