trace_irq_handler_entry(9)

💅 trace_irq_handler_entry — Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual entry for trace_irq_handler_entry, and trust me, this one is a little baddie. 🎀

---

🌸 NAME 🌸

trace_irq_handler_entry — the tracepoint that gets called, like, immediately before the irq action handler runs. literally the "hey bestie, they're about to go in" moment. 👀

---

✨ SYNOPSIS ✨

void trace_irq_handler_entry (int irq , struct irqaction *action );

two arguments, no return type, she just vibes in and does her thing. 🫶

---

🦋 ARGUMENTS 🦋

• irq — the irq number 💅 like, which interrupt we're talking about
• action — a pointer to struct irqaction — yes queen, a whole pointer, we love to see it

---

🧚 DESCRIPTION 🧚

so the struct irqaction that action points at? it's giving information central. it holds all kinds of stuff about the handler, including:

• the device name, action->name 🌸
• the device id, action->dev_id 🎀

and here's the iconic part, bestie — when you use this in conjunction with the irq_handler_exit tracepoint, we can figure out irq handler latencies. no cap. you get the "before" here, the "after" over there, and the difference is the tea. ☕✨

---

🔥 SEE ALSO 🔥

• Kernel file ./include/trace/events/irq.h
• trace_irq_handler_exit(9)
• trace_softirq_entry(9)
• trace_softirq_exit(9)
• trace_softirq_raise(9)
• trace_tasklet_entry(9)
• trace_tasklet_exit(9)

---

and that's the whole page, bestie, no notes. 💖 this little gem lives in ./include/trace/events, dated October 2026, and it's brought to you by the Kernel API Manual herself. periodt. 👑🌈