STRUCT MSM_VM_MAP_OP(9)

💅 struct msm_vm_map_op(9) 💅

okay bestie, welcome to the Kernel API Manual — this page is all about struct msm_vm_map_op, the lil struct for create new pgtable mapping. No cap, it’s giving “one job, but make it carry every detail.” ✨

🌸 NAME 🌸

• struct msm_vm_map_op — create new pgtable mapping

✨ SYNOPSIS ✨

struct msm_vm_map_op {
    uint64_t iova;
    uint64_t range;
    uint64_t offset;
    struct sg_table *sgt;
    int prot;
    int queue_id;
 };

🎀 Members 🎀

okay, let’s do a vibe check on every member — yes, all six, we are not skipping any 💖

• iova — start address for mapping. That’s the opening act, fr fr.
• range — size of the region to map. The way it just tells you how much 🎀
• offset — offset into sgt to map.
• sgt — pages to map, or NULL for a PRR mapping. Iconic.
• prot — the mapping protection flags.
• 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).

🦋 SEE ALSO 🦋

if you’re doing a deep dive, bestie, these are the pages and the kernel file to hit next:

• Kernel file ./drivers/gpu/drm/msm/msm_gem_vma.c
• struct msm_vm_unmap_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)

🫶 that’s the whole page, no notes: source spot is ./drivers/gpu/drm/msm, dated October 2026, and it’s filed under the Kernel API Manual as struct msm_vm_map_op(9). mwah 💋