dma_iova_sync(9)

okay so bestie, welcome to dma_iova_sync(9) from the Kernel API Manual 🫶 this one is short but iconic, and we are gonna read it together, no cap ✨

💅 NAME

dma_iova_sync — Sync IOTLB

---

✨ SYNOPSIS

int dma_iova_sync (struct device *dev , struct dma_iova_state *state ,
       size_t offset , size_t size );

🎀 ARGUMENTS

• dev — DMA device. The device doing the DMA thing, basically the main character here 💅
• state — IOVA state. Yep, that state.
• offset — offset into the IOVA state to sync. It tells you where in the state we're syncing from.
• size — size of the buffer. How big the buffer is, periodt.

---

🦋 DESCRIPTION

okay so the whole vibe: sync the IOTLB for the given IOVA state 🌈✨

This function should be called on the IOVA-contiguous range created by one ore more dma_iova_link calls, and its job is to sync the IOTLB. Yes, “ore” is literally what it says, and yes I am preserving it fr fr 💀🙈

bestie, the key detail is that “should be called” on that IOVA-contiguous range from one ore more dma_iova_link calls — that is the whole instruction, no cap.

---

🌸 SEE ALSO

Kernel file ./drivers/iommu/dma-iommu.c — go peek, iykyk 👑

• iommu_get_dma_cookie(9)
• iommu_get_msi_cookie(9)
• iommu_put_dma_cookie(9)
• iommu_put_msi_cookie(9)
• iommu_dma_get_resv_regions(9)
• iommu_dma_init_options(9)
• iommu_dma_init_domain(9)
• dma_info_to_prot(9)
• dma_iova_try_alloc(9)
• dma_iova_free(9)
• dma_iova_link(9)
• dma_iova_unlink(9)
• dma_iova_destroy(9)

---

mwah 💋 this lil page’s source/version is ./drivers/iommu, and it’s dated October 2026 — iconic, stamped, done 🎀✨