irq_inject_interrupt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, welcome to the irq_inject_interrupt(9) page from the Kernel API Manual πŸ’… β€” this one is all about irq_inject_interrupt, and its whole job is literally: inject an interrupt for testing/error injection. That’s the vibe. ✨

✨ SYNOPSIS ✨

here’s the exact signature, no cap:

int irq_inject_interrupt (unsigned int irq );

πŸŽ€ ARGUMENTS πŸŽ€

  • irq β€” the interrupt number. that’s the one you’re handing over 🫢

πŸ’… DESCRIPTION πŸ’…

⚠️ bestie, listen: this function must only be used for debug and testing purposes! like, do not make this a whole production situation, okay? 😭

especially on x86, this can cause a premature completion of an interrupt affinity change, causing the interrupt line to become stale. Very unlikely, but possible. so yeah β€” highkey β€œhandle with care” energy πŸ’€

the injection can fail for various reasons:

  • Interrupt is not activated
  • Interrupt is NMI type or currently replaying
  • Interrupt is level type
  • Interrupt does not support hardware retrigger and software resend is either not enabled or not possible for the interrupt

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./kernel/irq/resend.c β€” go read it if you want the full lore πŸ“–

and that’s the whole page, bestie 🫢 source/version: ./kernel/irq, date: October 2026 β€” mwah πŸ’‹

πŸ“¦ where this page comes from