viortc_alloc_vq_bufs(9)

📦 version 7.3.1, in nixpkgs unstable

💖 viortc_alloc_vq_bufs(9) — like, the alarmq buffer allocator 💖

okay bestie, welcome to the Kernel API Manual ✨ this one's about viortc_alloc_vq_bufs, and yes the name is a mouthful but it's literally just "allocate alarmq buffers" — that's the whole vibe, the whole job, the whole main character moment 🎀

✨ NAME ✨

viortc_alloc_vq_bufs — allocate alarmq buffers 🦋

🌸 SYNOPSIS 🌸

int viortc_alloc_vq_bufs (struct viortc_dev *viortc , unsigned int
num_elems , u32 buf_cap );

like… it takes three things and gives you back an int. that's it. that's the whole signature, no cap 💅

🎀 ARGUMENTS 🎀

  • viortc — the device data. it's your device, your struct viortc_dev *, your little guy 🫶
  • num_elems — the # of buffers. how many bestie. how many buffers are we making ✨
  • buf_cap — per-buffer device-writable bytes. so, capacity, but make it per-buffer, and make it device-writable 💖

🧚 CONTEXT 🧚

Process context. periodt. that's the whole context section, she's a short queen 👑

ngl do not try to be cute and call this from somewhere spicy — it says process context, so that's the assignment, no notes 🙈

⭐ RETURN ⭐

Zero on success, negative error code otherwise. like every good kernel function — 0 means slay, anything negative means it's giving error 🔥

💜 SEE ALSO 💜

buckle up bestie, this list is long — but every single one of these is iconic in her own right, so we're listing all of them, fr fr:

and that's the page!! 🎉 this little icon lives under ./drivers/virtio and she's dated October 2026 — mwah, go read the other ones, iykyk 💅💖🦋

📦 where this page comes from