PROBE::IRQ_HANDLER.EXIT(3stap)

💖 PROBE::IRQ_HANDLER.EXIT — the 3stap girlies know 💖

okay so bestie, welcome to the Interrupt Request (IRQ) Tapset 🌸 this is a 3stap manual page and honestly? she's a baddie. sit down, grab a strawberry 🍓, and let's get into it.

---

✨ NAME ✨

probe::irq_handler.exit — the interrupt handler finished doing her thing. that's it, that's the moment. execution complete 👑

---

🦋 SYNOPSIS 🦋

probe irq_handler.exit {}

no args, no drama, no notes. just vibes 💅

---

🎀 VALUES 🎀

these are all the little cuties this probe hands you. every single one, no gatekeeping 🫶

• flags_str — a symbolic string representation of the IRQ flags. like, the flags but in words ✨
• dev_name — name of the device. what's her name? 💖
• action — a struct irqaction*. yeah, it's a pointer, it's giving raw energy 😭
• handler — the interrupt handler function that was actually executed. the main character of this whole situation 👑
• next_irqaction — pointer to the next irqaction, for when interrupts are shared. she's not alone, she's in a group chat 🌈
• thread_flags — flags related to the thread 🧵
• dir — pointer to the proc/irq/NN/name entry 📁
• flags — flags for the IRQ handler. yes, there's also flags_str up top, they're different, don't @ me 💀
• ret — the return value of the handler. what did she decide? 🙈
• dev_id — a cookie used to identify the device 🍪 iconic honestly
• thread_fn — the interrupt handler function for threaded interrupts 🧚
• thread — thread pointer for threaded interrupts 🧵✨
• irq — the interrupt number 🔢

no cap, that's every single value. i counted. twice. 💅

---

🌸 SEE ALSO 🌸

• tapset::irq(3stap) — go read this one too, she's the blueprint 🎀

---

and that's the page bestie!! SystemTap Tapset Reference, Ver, September 2026 — literally a classic. mwah 💋 stay curious, read your tapsets, and remember: interrupt handlers finish, but the lore never does 🦋✨💖