p9_virtio_create(9)

💖 NAME 💖

p9_virtio_create — bestie, this one allocates a brand new virtio channel ✨

(it's from the Kernel API Manual, iykyk 🎀)

---

🌸 SYNOPSIS 🌸

int p9_virtio_create (struct p9_client *client , struct fs_context *fc );

---

🦋 ARGUMENTS 🦋

• client — the client instance that's out here invoking this transport, main character energy fr 👑
• fc — the filesystem context, that's it, that's the whole vibe 🫶

---

🧚 DESCRIPTION 🧚

Okay so what this does is it sets up a transport channel for 9p communication 💅 like, that's the whole job.

Right now we only match the first available channel — no cap, that's genuinely all it does at the moment 🙈. But eventually (future us is gonna slay, trust) we could look up alternate channels by matching devname versus a virtio_config entry. So like, the door's open for that ✨.

And the way it keeps things chill: we use a simple reference count mechanism to ensure that only a single mount has a channel open at a time 🔥. One mount, one channel, periodt. No fighting over resources, we don't do that here 💀.

Not gonna lie, the "only the first available channel" part is the lowkey catch — it's literally the current behaviour, so don't go expecting alternate channel lookups to work just yet 🍓.

---

⭐ SEE ALSO ⭐

• Kernel file ./net/9p/trans_virtio.c struct virtio_chan(9)
• p9_virtio_close(9)
• req_done(9)
• pack_sg_list(9)
• pack_sg_list_p(9)
• p9_virtio_request(9)
• p9_virtio_zc_request(9)
• p9_virtio_probe(9)
• p9_virtio_remove(9)

Go read those, they're all iconic in their own way 🌈💜

---

Okay that's the whole page bestie, ily, go touch some kernel code 🧚‍♀️💖

This one lives under ./net/9p and it's dated October 2026 — screenshot it, frame it, whatever, it's giving archival icon behavior 🎀✨