msi_domain_alloc_irqs_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… msi_domain_alloc_irqs_range(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this page is literally about msi_domain_alloc_irqs_range, and it's giving β€œallocate a whole range of interrupts from a MSI interrupt domain” main-character energy. No cap. πŸ¦‹


🌸 NAME 🌸

msi_domain_alloc_irqs_range β€” allocate interrupts from a MSI interrupt domain. πŸŽ€


✨ SYNOPSIS ✨

int msi_domain_alloc_irqs_range (struct device *dev , unsigned int domid
, unsigned int first , unsigned int last );

This signature is exact, character-for-character. Keep it cute, keep it correct. πŸ’–


πŸ‘‘ ARGUMENTS πŸ‘‘

  • dev β€” pointer to the device struct of the device for which the interrupts are allocated. This is the device whose interrupt situation we're handling. 🫢
  • domid β€” Id of the interrupt domain to operate on. Yes, the domain id, not a vibe id. πŸ’…
  • first β€” first index to allocate, and it's inclusive β€” like, it counts. πŸ“
  • last β€” last index to allocate, also inclusive β€” both ends are invited to the party. πŸŽ€

πŸ”₯ RETURN πŸ”₯

It returns 0 on success or an error code. That's the whole return vibe: success is 0, anything else is an error code. 😭


🌈 SEE ALSO 🌈

Kernel file ./kernel/irq/msi.c is the source-file bestie, and here's the full friend group in original order:


Signed with glitter and good vibes from the ./kernel/irq source corner of the Kernel API Manual, dated October 2026 β€” mwah πŸ’–βœ¨

πŸ“¦ where this page comes from