virtio_dma_buf_export(9)

💅 virtio_dma_buf_export — like, the section 9 girlies already know

Okay so bestie, welcome to virtio_dma_buf_export(9), the kernel API manual page. Yes it's a 9, yes that means kernel internals, yes we're doing this. Pull up a chair 🎀

---

✨ NAME ✨

virtio_dma_buf_export — creates a new dma-buf for a virtio exported object. That's it, that's the whole job. She's a builder 💅

---

✨ SYNOPSIS ✨

struct dma_buf * virtio_dma_buf_export (const struct dma_buf_export_info
*exp_info );

Copy it exactly like that if you're typing it, bestie, don't get creative 🙈

---

✨ ARGUMENTS ✨

• exp_info — [in] okay so for the deets you gotta go see dma_buf_export. But the one thing you CANNOT skip: the ops field MUST refer to a dma_buf_ops struct that's embedded in a virtio_dma_buf_ops. Capital-M Must, no cap. Not "should", not "ideally", MUST 🔥

---

✨ DESCRIPTION ✨

So basically this wraps dma_buf_export — like a little glamorous coat, a little cardigan over the function — so that virtio drivers can create a dma-buf for a virtio exported object. And why do we care? Because that object's UUID can then be queried by other virtio drivers. It's giving sharing is caring, it's giving cross-driver communication, it's giving community 🫶

Literally the whole point is that UUID lookup, and this is the function that makes it possible. Iconic.

---

✨ SEE ALSO ✨

• Kernel file ./drivers/virtio/virtio_dma_buf.c — the source, go read her, she's right there
• virtio_dma_buf_attach(9)
• is_virtio_dma_buf(9)
• virtio_dma_buf_get_uuid(9)

Go read the whole friend group, they're all connected, iykyk 🦋

---

Heads up bestie: that ops-must-be-an-embedded-virtio_dma_buf_ops rule from ARGUMENTS is not a vibe suggestion. Treat it as law. ⭐

---

And that's the page! 🌸 Little sign-off moment: this gem lives in ./drivers/virtio, stamped October 2026, and it's virtio_dma_buf_export(9) forever and always. Slay, go export something 💖👑