tracepoint_probe_register(9)
π tracepoint_probe_register π
okay bestie, welcome to the Kernel API Manual β yes, that's the manual name, we're in the kernel section, section 9, and this is THE page for tracepoint_probe_register. buckle up π
β¨ NAME β¨
tracepoint_probe_register β Connect a probe to a tracepoint π«Ά
like, literally hooking your little probe handler onto a tracepoint. match made in heaven, no cap.
πΈ SYNOPSIS πΈ
int tracepoint_probe_register (struct tracepoint *tp , void *probe ,
void *data );
look at her go π iconic signature fr fr.
π¦ ARGUMENTS π¦
tpβ tracepoint. the main character of this whole situation πprobeβ probe handler. this is the function doing the actual work πͺdataβ tracepoint data. the little sidekick that gets passed along π
π DESCRIPTION π
Returns 0 if ok, error value on error. that's it, that's the vibe β¨
β NOTE β
β οΈ okay listen up, this part is important, do NOT skip it:
if tp is within a module, the caller is responsible for unregistering the probe before the module is gone. yes, you, bestie β it's on you π
This can be performed either with a tracepoint module going notifier, or from within module exit functions. pick your fighter π
π₯ SEE ALSO π₯
- Kernel file
./kernel/tracepoint.c tracepoint_probe_register_prio_may_exist(9)tracepoint_probe_register_prio(9)tracepoint_probe_unregister(9)register_tracepoint_module_notifier(9)unregister_tracepoint_module_notifier(9)for_each_tracepoint_in_module(9)for_each_module_tracepoint(9)for_each_kernel_tracepoint(9)
the whole friend group honestly ππ
β¨ and that's the page, bestie β¨ this little icon comes from ./kernel, dated October 2026, and it's brought to you by the kernel API manual gang β go forth and register those probes responsibly π§ββοΈπ
π
π¦ 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