pci_alloc_ir...ors_affinity(9)

okay so bestie, this is the Kernel API Manual page for pci_alloc_irq_vectors_affinity — the header writes it as pci_alloc_ir...ors_affinity(9), but the full function name is the one we're working with 💖

🌸 NAME 🌸

pci_alloc_irq_vectors_affinity — allocates multiple device interrupt vectors with affinity requirements. That's the whole name-section snack, periodt ✨

✨ SYNOPSIS ✨

int pci_alloc_irq_vectors_affinity (struct pci_dev *dev , unsigned int
min_vecs , unsigned int max_vecs , unsigned int flags , struct
irq_affinity *affd );

🎀 ARGUMENTS 🎀

• dev — the PCI device to operate on, bestie. This is the device getting the interrupt-vector glow-up.
• min_vecs — minimum required number of vectors. And listen: it must be >= 1, no cap.
• max_vecs — maximum desired number of vectors. It's giving upper-limit energy.
• flags — allocation flags, as in pci_alloc_irq_vectors. Same flag vibe, different function.
• affd — affinity requirements. It can be NULL, so no pressure if you don't have affinity demands.

bestie, do not forget the min_vecs rule: it must be >= 1. The kernel is not accepting zero-vector chaos 💀

🦋 DESCRIPTION 🦋

Same as pci_alloc_irq_vectors, but with the extra affd parameter. That's the whole plot twist 💅

Check that function's docs, and struct irq_affinity, for more details. Those are your lore drops, iykyk 🫶

💜 SEE ALSO 💜

• Kernel file ./drivers/pci/msi/api.c
• pci_enable_msi(9)
• pci_disable_msi(9)
• pci_msix_vec_count(9)
• pci_enable_msix_range(9)
• pci_msix_can_alloc_dyn(9)
• pci_msix_alloc_irq_at(9)
• pci_msix_free_irq(9)
• pci_disable_msix(9)
• pci_alloc_irq_vectors(9)
• pci_irq_vector(9)
• pci_irq_get_affinity(9)
• pci_free_irq_vectors(9)
• pci_restore_msi_state(9)
• pci_msi_enabled(9)

kisses bestie 💋 — this page came from the ./drivers/pci/msi source, dated October 2026, and signs off as pci_alloc_ir...ors_affinity(9). slay and bye 🫶