tracepoint_p...io_may_exist(9)

💫 NAME 💫

tracepoint_probe_register_prio_may_exist — ok so this one hooks a probe up to a tracepoint, but like… with a priority. And it's the chill version that does not warn you if the tracepoint is already registered. Bestie behaviour fr fr 🫶

(this lives in the Kernel API Manual, section 9, iykyk ✨)

---

🌸 SYNOPSIS 🌸

int tracepoint_probe_register_prio_may_exist (struct tracepoint *tp ,
       void *probe , void *data , int prio );

---

🎀 ARGUMENTS 🎀

• tp — the tracepoint itself, the main character of this whole situation 👑
• probe — the probe handler, aka the function that actually does the thing
• data — the tracepoint data, just vibes and payload 🍓
• prio — the priority of this function over the other registered functions, so like… who goes first 💅

---

🦋 DESCRIPTION 🦋

Literally the same as tracepoint_probe_register_prio, no cap — the only glow-up here is that it will not warn if the tracepoint is already registered. That's it. That's the whole personality. 🙈

So yes, it's the same deal as tracepoint_probe_register_prio in every other way. Don't go expecting extra magic, bestie 💖

---

⭐ SEE ALSO ⭐

Kernel file ./kernel/tracepoint.c — go read it, it's giving source of truth 🌈

• tracepoint_probe_register_prio(9)
• tracepoint_probe_register(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)

---

ok that's the whole page, you ate that 🧚💜 this cutie is from ./kernel, version October 2026, and the page name is tracepoint_p...io_may_exist(9) in case you forgot already — go register some probes, slay ✨🔥