msi_domain_get_virq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… msi_domain_get_virq(9) β€” from the Kernel API Manual, bestie πŸŽ€

okay so picture this: you're deep in the Linux kernel, you've got a device, you've got a domain, you've got an index, and what you really need is the interrupt number. That's the whole plot of msi_domain_get_virq. She's the lookup girlie. The one who finds the Linux interrupt number for a MSI index on a interrupt domain. No cap, that's literally the job description ✨


πŸ¦‹ NAME πŸ¦‹

msi_domain_get_virq β€” Lookup the Linux interrupt number for a MSI index on a interrupt domain πŸ’–


🌸 SYNOPSIS 🌸

unsigned int msi_domain_get_virq (struct device *dev , unsigned int
domid , unsigned int index );

✨ ARGUMENTS ✨

  • dev β€” the Device you're operating on, your main character of the moment 🫢
  • domid β€” the Domain ID of the interrupt domain that's associated to the device πŸ‘‘
  • index β€” the MSI interrupt index you're looking for, and yes bestie it's 0-based, so index 0 is a real and valid thing, don't do her dirty πŸ™ˆ

πŸ’€ RETURN πŸ’€

The Linux interrupt number on success (that's > 0), or 0 if it's not found 😭

fr fr, if you get a 0 back, that's not a pointer to nothing, that's the "nope, didn't find it" signal. zero means zero here.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./kernel/irq/msi.c β€” and the whole rest of the squad πŸ’œ


and that's the page babes 🌈 this little gem lives under ./kernel/irq and the version on deck is dated October 2026 β€” go forth, look up those interrupt numbers, slay, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from