STRUCT VIRTQUEUE_INFO(9)

✨ struct virtqueue_info(9) ✨

okay so bestie, welcome to the Kernel API Manual — this is the page for struct virtqueue_info, and honestly? it's giving "small struct, big responsibilities" 💅

---

🌸 NAME 🌸

struct virtqueue_info — literally the info for a virtqueue that gets passed to find_vqs(). that's it, that's the whole vibe 🎀

---

🦋 SYNOPSIS 🦋

struct virtqueue_info {
    const char *name;
    vq_callback_t *callback;
    bool ctx;
 };

like, three members. tiny. iconic. she does exactly what she needs to do and nothing more 👑

---

💖 Members 💖

okay so let's go member by member, because each one has main character energy in her own way:

• name — the virtqueue description. it's used mainly for debugging, so like, it's the little name tag she wears at the party 🏷️ and yeah — set it to NULL for a virtqueue that's unused by the driver. no name tag, no party, no problem.
• callback — a callback to invoke on a used buffer notification. think of it as her phone number for when something's ready 📞 and again: NULL for a virtqueue that does not need a callback. she's off duty, don't call her.
• ctx — whether to maintain an extra context per virtqueue. yes/no, true/false, do we keep extra context or not 🫶 that's the whole question.

ngl bestie, name and callback both being NULL-able is very much "I'm flexible, I contain multitudes" and we love that for her 💀

---

🔥 SEE ALSO 🔥

go read these next, they're all connected, iykyk:

• the Kernel file ./include/linux/virtio_config.h
• struct virtio_config_ops(9)
• struct virtio_map_ops(9)
• __virtio_test_bit(9)
• __virtio_set_bit(9)
• __virtio_clear_bit(9)
• virtio_has_feature(9)
• virtio_has_dma_quirk(9)
• virtio_synchronize_cbs(9)
• virtio_device_ready(9)
• virtqueue_set_affinity(9)

---

💜 one last thing bestie — this whole page lives in ./include/linux, and it's dated October 2026, and the page itself is struct virtqueue_info(9). so yeah, go forth, pass your info to find_vqs(), and slay ✨💅🦋