pci_msi_domain_get_msi_rid(9)

✨ pci_msi_domain_get_msi_rid 💅

okay so bestie, welcome to the Kernel API Manual — we're looking at pci_msi_domain_get_msi_rid(9) today and honestly? it's a little legend. the whole vibe is: Get the MSI requester id (RID) 🎀

---

🌸 SYNOPSIS 🌸

u32 pci_msi_domain_get_msi_rid (struct irq_domain *domain , struct
pci_dev *pdev );

like, that's the whole signature. no cap. 🫶

---

🦋 ARGUMENTS 🦋

• domain — the interrupt domain, aka the whole little ecosystem we're poking at 💫
• pdev — the PCI device. the actual device. the main character of this story 👑

---

💖 DESCRIPTION 💖

so here's the tea: the RID for a device? it gets formed from the alias, with a firmware supplied mapping applied on top. that's it, that's the whole glow-up. ✨

ngl the "firmware supplied mapping" part is doing a lot of heavy lifting here — it's the glow-up layer on top of the alias, iykyk 🧚

---

🌈 RETURN 🌈

it returns the RID. that's the answer. the RID. 💅

like literally, u32, the RID, done, periodt.

---

⭐ SEE ALSO ⭐

the kernel file lives at ./drivers/pci/msi/irqdomain.c and here's the whole friend group you should also go say hi to:

• pci_msi_domain_write_msg(9)
• pci_setup_msi_device_domain(9)
• pci_setup_msix_device_domain(9)
• pci_msi_domain_supports(9)
• pci_msi_map_rid_ctlr_node(9)
• pci_msi_get_device_domain(9)

---

okay that's the whole page bestie, go get that RID 🔥

mwah 💋 — this lil page lives in ./drivers/pci/msi, dropped October 2026, straight from the Kernel API Manual, and yes it's still called pci_msi_domain_get_msi_rid(9) at the bottom too, iconic of it honestly 🎀