virtqueue_ma...e_for_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

okay so bestie, welcome to the Kernel API Manual ✨ — today's main character is virtqueue_map_sync_single_range_for_device 🎀 and what it does is map sync for device 🫶

✨ SYNOPSIS ✨

void virtqueue_map_sync_single_range_for_device (const struct virtqueue
*_vq , dma_addr_t addr , unsigned long offset , size_t size , enum
dma_data_direction dir );

like, that's the whole signature, no cap 💖

🌸 ARGUMENTS 🌸

  • _vq — the struct virtqueue we're talking about 💫 literally the vq in question
  • addr — DMA address 📍
  • offset — DMA address offset, like how far in we're going 🎯
  • size — buf size for sync, i.e. how much we're syncing 🧚
  • dir — DMA direction, which way the data's vibing ➡️

🦋 DESCRIPTION 🦋

okay so listen 🔥 before you call this function, you gotta use virtqueue_map_need_sync to confirm that the DMA address really needs to be synchronized 👑

no fr, do the vibe check first — virtqueue_map_need_sync is the pre-check, don't skip it 🙈

like it's giving "look before you leap" but for DMA addresses 💅

⭐ SEE ALSO ⭐

the whole friend group 🫶 — kernel file ./drivers/virtio/virtio_ring.c and:

k byeee 💜 this one came out of ./drivers/virtio dated October 2026, and the page itself is virtqueue_ma...e_for_device(9) — mwah, stan, periodt 🌈✨

📦 where this page comes from