rproc_add_virtio_dev(9)

💅 rproc_add_virtio_dev(9) 💅

okay so before we even get into it — hi bestie, welcome to the Kernel API Manual ✨ this one's a short one but it's kind of a big deal, no cap. it's giving "tiny function, main character energy" 🎀

---

🌸 NAME 🌸

rproc_add_virtio_dev — registers an rproc-induced virtio device 🦋

like, it's the function that literally makes the virtio device show up. iconic behavior tbh 👑

---

✨ SYNOPSIS ✨

int rproc_add_virtio_dev (struct rproc_vdev *rvdev , int id );

that's it. two args. she's simple, she's clean, she slays 💅

---

🫶 ARGUMENTS 🫶

• rvdev — the remote vdev 💖 this is the remote virtio device struct you're handing over, bestie, and yes it needs to be a struct rproc_vdev *.
• id — the device type identification 🔥 and like, its whole job is to match the device up with a driver. that's the matchmaking moment. iykyk 💫 (it's an int, before you ask)

---

🧚 DESCRIPTION 🧚

so what does it actually do? it registers a virtio device ✨ that's the whole vibe. one job, done well, periodt.

and the little detail that matters: this vdev's parent is the rproc device 👑 like the rproc is the parent and the vdev is the baby, the family tree is intact, we love a functional household 🌈

---

⭐ RETURN ⭐

• 0 on success 🎉 (the slay case)
• or an appropriate error value otherwise 💀 (the "oop" case — check it, don't just assume you ate)

---

👀 SEE ALSO 👀

• Kernel file ./drivers/remoteproc/remoteproc_virtio.c — go read the source, bestie, it's literally right there 🍓
• rproc_vq_interrupt(9) — the interrupt one 🦋
• rproc_remove_virtio_dev(9) — the one that undoes this one 😭 (every add has its remove, that's just life)

---

okay that's the whole thing!! short, sweet, and honestly kind of a baddie 🧚💜

sign-off time: this little beauty lives in ./drivers/remoteproc, dated October 2026 🎀 mwah, go register some virtio devices responsibly, ily 💖✨