STRUCT MSM_VM_UNMAP_OP(9)

✨ NAME ✨

okay so bestie, this is the page for struct msm_vm_unmap_op(9) from the Kernel API Manual, and it is literally unmap a range of pages from pgtable 💅. That’s the whole vibe: this struct is the “bye-bye, pages” situation for a chunk of page-table mappings. No cap.

🌸 SYNOPSIS 🌸

here’s the exact shape of it, bestie 🫶:

       struct msm_vm_unmap_op {
           uint64_t iova;
           uint64_t range;
           const char *reason;
           int queue_id;
        };

🎀 Members 🎀

• iova — start address for unmap. That’s where the unmap begins, bestie ✨.
• range — size of region to unmap. Like, how much we’re unmapping 💅.
• reason — The reason for the unmap. Yes, it keeps receipts 🧾.
• queue_id — The id of the submitqueue the operation is performed on, or zero for (in particular) UNMAP ops triggered outside of a submitqueue (ie. process cleanup). Zero is the special-case icon here 👑.

🔥 SEE ALSO 🔥

Kernel file ./drivers/gpu/drm/msm/msm_gem_vma.c is the source-adjacent baddie, and the related crew is:

• struct msm_vm_map_op(9)
• struct msm_vm_op(9)
• struct msm_vm_bind_job(9)
• msm_gem_vm_unusable(9)
• msm_gem_vm_create(9)
• msm_gem_vm_close(9)

later, bestie 💖 — source/version: ./drivers/gpu/drm/msm, date: October 2026, page: struct msm_vm_unmap_op(9). mwah 💋