STRUCT IRQ_REDIRECT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ struct irq_redirect(9) πŸŽ€

okay so this is a page from the Kernel API Manual bestie, and it's literally all about struct irq_redirect β€” the ✨interrupt redirection metadata✨ of it all. tiny struct, big main character energy, let's get into it πŸ’…


🌸 NAME 🌸

struct irq_redirect β€” interrupt redirection metadata πŸ¦‹

like, it's the little bundle of info that keeps track of where an interrupt is headed. no cap.


✨ SYNOPSIS ✨

struct irq_redirect {
    struct irq_work work;
    unsigned int    target_cpu;
 };

that's the whole vibe. two members, zero drama 🫢


πŸ’– Members πŸ’–

  • work β€” a Harg irq_work item, and its whole job is handler execution on a different CPU. yes the page literally says Harg, that's not me being silly, I'm quoting the source bestie 😭 it's the irq_work item, periodt.
  • target_cpu β€” the CPU to run the irq handler on, in case the current CPU is not part of the irq affinity mask. so like, if your current CPU isn't invited to the party, this is the CPU that is πŸŽ‰ an unsigned int, iconic.
🌟 quick vibe check: target_cpu only kicks in when the current CPU isn't in the irq affinity mask. it's the backup plan, the understudy, the "girl you're not on the list but she is" of CPUs πŸ™ˆ

🌈 SEE ALSO 🌈

go look at the kernel file ./include/linux/irqdesc.h and the whole friend group:


and that's the page bestie! πŸ’–βœ¨ straight out of ./include/linux, dated October 2026, no thoughts just interrupt redirection metadata. mwah πŸŽ€πŸ’…πŸŒŸ

πŸ“¦ where this page comes from