msi_domain_...range_locked(9)

📦 version 7.3.1, in nixpkgs unstable

✨ msi_domain_free_irqs_range_locked — the kernel API manual page, bestie edition 💅

okay so this is straight out of the Kernel API Manual (yes, the msi_domain_...range_locked(9) one, that's our girl) and it's genuinely so specific and I'm obsessed. let's get into it 🫶

🌸 NAME 🌸

msi_domain_free_irqs_range_locked — frees a whole range of interrupts from an MSI interrupt domain that's associated to @dev, and does it with msi_lock held. like, the lock is already yours, you're just doing the thing 🔥

✨ SYNOPSIS ✨

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

that's the whole signature. returns nothing (void), takes four things, slays 💅

🎀 ARGUMENTS 🎀

  • dev — pointer to the device struct of the device whose interrupts are getting freed. it's her device, we're cleaning up her stuff 🌸
  • domid — the id of the interrupt domain we're operating on. gotta know which domain you're in iykyk 🦋
  • first — the first index to free, and yes it's inclusive 💖
  • last — the last index to free, also inclusive. so the range is first..last, both ends in, no cap 🌈

🔥 SEE ALSO 🔥

the whole friend group, in the original order, no one gets left out 👑

Kernel file ./kernel/irq/msi.c, plus:

lowkey the most important vibe check here: the _locked in the name is not decorative, bestie — this one expects msi_lock to already be held. don't come in unlocked, that's not the move 💀

and that's the page!! this lil icon comes to you from ./kernel/irq, dated October 2026 — mwah, go free those interrupts responsibly 💖🎀✨

📦 where this page comes from