ntb_msi_peer_trigger(9)

💫 ntb_msi_peer_trigger — like, the Kernel API Manual page, bestie ✨

okay so bestie, we're in the Kernel API Manual today and this one is genuinely such a slay little function. it's giving "reach out and poke your friend" energy and honestly? iconic. let's get into it 🫶

---

🌸 NAME 🌸

ntb_msi_peer_trigger — trigger an interrupt handler on a peer 💅

---

🦋 SYNOPSIS 🦋

int ntb_msi_peer_trigger (struct ntb_dev *ntb , int peer , struct
       ntb_msi_desc *desc );

like yes, that's the whole signature, no cap ✨

---

🎀 ARGUMENTS 🎀

• ntb — the NTB device context 🧚 (the whole vibe of a device we're working with)
• peer — the peer index, aka which friend we're poking 👑
• desc — the MSI descriptor data which triggers the interrupt ⭐ this is the actual thing that makes the interrupt happen

---

🔥 DESCRIPTION 🔥

so this function triggers an interrupt on a peer. literally that's the whole job and it ate 💀

the one thing to know — the important part, don't skip it — is that it requires the descriptor structure to have been passed from that peer by some other means. so like, desc has to get to you through some other channel first; this function isn't out here manifesting descriptors out of thin air, periodt. you gotta have the goods before you can use them, iykyk 🍓

---

🌈 RETURN 🌈

• Zero on success 🎉
• otherwise, a negative error number 😭 (main character energy only when it works, bestie)

---

👀 SEE ALSO 👀

• Kernel file ./drivers/ntb/msi.c 📁
• ntb_msi_init(9)
• ntb_msi_setup_mws(9)
• ntb_msi_clear_mws(9)
• ntbm_msi_request_threaded_irq(9)

go read those too, they're all part of the same friend group fr fr 💜

---

and that's the whole page, bestie!! this one lives over in ./drivers/ntb and it's dated October 2026 📅 — so like, future vibes, we love to see it. mwah, go trigger some interrupts responsibly 💅💖✨