update_ftrace_direct_add(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ update_ftrace_direct_add(9) πŸ¦‹

okay bestie, this page is from the Kernel API Manual, and it's all about that ftrace direct-caller update life. No cap, it's giving kernel-internals main character energy. πŸ’…


🌸 NAME 🌸

update_ftrace_direct_add β€” updates @ops by adding direct callers provided in @hash. ✨

✨ SYNOPSIS ✨

int update_ftrace_direct_add (struct ftrace_ops *ops , struct ftrace_hash *hash );

πŸŽ€ ARGUMENTS πŸŽ€

  • ops β€” the address of the struct ftrace_ops object. πŸ‘‘
  • hash β€” the address of the struct ftrace_hash object. 🫢

πŸ’– DESCRIPTION πŸ’–

This is the function you use to add custom direct callers (ip -> addr) to ops, specified in hash. The ops will be either registered or updated. That's it, that's the vibe. πŸ¦‹

πŸ”₯ RETURN πŸ”₯

zero on success. Non zero on error, and that error list includes: -EINVAL β€” the hash is empty. 😭

🌈 SEE ALSO 🌈

Kernel file ./kernel/trace/ftrace.c β€” and here's the whole squad, no cap:


xoxo πŸ’‹ β€” this page's source/version spot is ./kernel/trace, and it's dated October 2026; it's the Kernel API Manual, bestie. πŸŽ€

πŸ“¦ where this page comes from