msi_domain_first_desc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ msi_domain_first_desc ✨

okay so bestie, welcome to the msi_domain_first_desc(9) glow-up β€” it's a Kernel API Manual page and it's literally about grabbing the first MSI descriptor of an irqdomain that's associated to a device. one descriptor. first one. main character energy only πŸ’…


πŸ’– NAME πŸ’–

msi_domain_first_desc β€” get the first MSI descriptor of an irqdomain associated to a device πŸŽ€


🌸 SYNOPSIS 🌸

struct msi_desc * msi_domain_first_desc (struct device *dev , unsigned
int domid , enum msi_desc_filter filter );

like, that's the whole signature, no cap 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device we're operating on, bestie. that's the one 🎯
  • domid β€” the id of the interrupt domain that should be walked. yes, walked. we're strolling through it πŸšΆβ€β™€οΈ
  • filter β€” the descriptor state filter. it filters. iconic behaviour ✨

πŸ’œ DESCRIPTION πŸ’œ

okay so this is the important one and I need you to listen 😭

Must be called with the MSI descriptor mutex held, i.e. msi_lock_descs must be invoked before the call.

like, msi_lock_descs before the call. not after. not "eh, it'll probably be fine". before. πŸ”’ no cap, this is not optional and honestly the kernel will not be cute about it πŸ’€


πŸ”₯ RETURN πŸ”₯

returns a pointer to the first MSI descriptor matching the search criteria πŸ’«

and if there's literally nothing that matches? NULL. none found. empty. the void. it's giving "nobody's home" πŸ™ˆ


🌈 SEE ALSO 🌈

like, that's a whole friend group and they all showed up πŸ«ΆπŸ‘‘


aaaand that's the page!! this one lives in the kernel tree at ./kernel/irq and it's stamped October 2026 β€” so yeah, she's from the future, we stan a forward-thinking queen πŸ‘‘πŸ’œβœ¨ periodt.

πŸ“¦ where this page comes from