pci_epc_set_msi(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pci_epc_set_msi(9) — like, the Kernel API Manual, bestie ✨

okay so real talk, this one's a whole function and it's lowkey the moment your endpoint decides how many MSI interrupt numbers it's gonna need. yes, this is the Kernel API Manual page for pci_epc_set_msi(9) and we're getting into it 🫶

🌸 SYNOPSIS 🌸

int pci_epc_set_msi (struct pci_epc *epc , u8 func_no , u8 vfunc_no , u8
nr_irqs );

like, that's the whole signature, no cap. four things in, int out 💅

🎀 ARGUMENTS 🎀

  • epc — the EPC device that's about to get its MSI configured. it's giving main character energy, everything happens on this one 👑
  • func_no — the physical endpoint function number, inside the EPC device. physical, bestie, keep that straight ✨
  • vfunc_no — the virtual endpoint function number, and it lives inside that physical function. so it's a function inside a function, very inception of it 🦋
  • nr_irqs — how many MSI interrupts the EPF is asking for. the actual number, the whole point, the icon 🎯

💖 DESCRIPTION 💖

invoke this when you need to set the required number of MSI interrupts. that's the whole vibe. you call it, and it sets the number of MSI interrupts required — genuinely that simple, and honestly? we love a one-job function 🧚

ngl the description is short but every word of it is carrying the entire page, so don't skip it 🙈

🦋 SEE ALSO 🦋

also check out the kernel file ./drivers/pci/endpoint/pci-epc-core.c — that's where the source lives, go read it, it's literally right there 📖

and then the whole extended friend group of related calls, all of them, in order, because we don't leave anyone out at this table:

✨ and that's the page, babes ✨

this little gem comes from ./drivers/pci/endpoint (that's the source, iykyk) and it's stamped October 2026 in the Kernel API Manual — so go forth, set those MSI numbers, and slay 💜🎀

📦 where this page comes from