rproc_vq_interrupt(9)

💅 NAME

rproc_vq_interrupt — bestie, this is the little function that tells remoteproc a virtqueue just got interrupted 👑

---

✨ SYNOPSIS

irqreturn_t rproc_vq_interrupt (struct rproc *rproc , int notifyid );

---

🎀 ARGUMENTS

• rproc — the handle to the remote processor. like, your whole entire connection to that far-away lil chip 🫶
• notifyid — the index of the signalled virtqueue, and yes it's unique per this rproc, no cap 🦋

---

🦋 DESCRIPTION

okay so this is the function your platform-specific rproc driver is supposed to call the moment the remote processor pings you like "hey, this specific virtqueue has pending messages available" 📬✨

that's it. that's the whole job. driver-side notification goes in, remoteproc finds out a virtqueue is poppin' off. iconic behaviour honestly 💅

---

🌸 RETURN

• IRQ_NONE — returned when no message was found in the notifyid virtqueue 😭 nothing there, tragic, empty queue energy
• IRQ_HANDLED — returned otherwise, i.e. there was something. slay 🔥

---

🔥 SEE ALSO

• Kernel file ./drivers/remoteproc/remoteproc_virtio.c
• rproc_add_virtio_dev(9)
• rproc_remove_virtio_dev(9)

---

kk that's the whole page, mwah 💖 this was the Kernel API Manual entry for rproc_vq_interrupt(9), living its best life in ./drivers/remoteproc, dated October 2026 — go forth and handle those interrupts, bestie 🌈👑