pvr_vm_gpuva_unmap(9)

💅 pvr_vm_gpuva_unmap(9) 💅

okay so welcome to the pvr_vm_gpuva_unmap(9) page from the Kernel API Manual, bestie. This is the little function that removes a mapping from a memory context — yes, that's the whole assignment, and it ate. 💖

🎀 NAME 🎀

pvr_vm_gpuva_unmap — Remove a mapping from a memory context. periodt, that's the name and the game.

✨ SYNOPSIS ✨

The signature is giving exactly this, no edits:

int pvr_vm_gpuva_unmap (struct drm_gpuva_op *op , void *op_ctx );

🧚 ARGUMENTS 🧚

• op — gpuva op containing the unmap details. basically the unmap lore packet 💅
• op_ctx — Operation context. the context for the operation, no cap.

🦋 CONTEXT 🦋

Called by drm_gpuvm_sm_unmap following a successful unmapping while op_ctx.vm_ctx mutex is held. So yeah, that's the exact situation: after a successful unmapping, with that mutex held. iykyk 🔥

🌸 RETURN 🌸

• 0 on success, or
• Any error returned by pvr_mmu_unmap.

that's the return tea, bestie 🍓

👑 SEE ALSO 👑

go give these cuties a look too 👀 — Kernel file ./drivers/gpu/drm/imagination/pvr_vm.c

• Memory context(9)
• struct pvr_vm_context(9)
• pvr_vm_get_page_table_root_addr(9)
• pvr_vm_get_dma_resv(9)
• Memory mappings(9)
• struct pvr_vm_gpuva(9)
• struct pvr_vm_bind_op(9)
• pvr_vm_bind_op_exec(9)
• pvr_vm_gpuva_map(9)
• pvr_vm_gpuva_remap(9)
• pvr_device_addr_is_valid(9)
• pvr_device_addr_and_size_are_valid(9)
• pvr_vm_create_context(9)
• pvr_vm_context_release(9)
• pvr_vm_context_lookup(9)
• pvr_vm_context_put(9)
• pvr_destroy_vm_contexts_for_file(9)
• pvr_vm_map(9)
• pvr_vm_unmap_obj_locked(9)
• pvr_vm_unmap_obj(9)
• pvr_vm_unmap(9)
• pvr_vm_unmap_all(9)
• pvr_heap_contains_range(9)
• pvr_find_heap_containing(9)
• pvr_vm_find_gem_object(9)
• pvr_vm_get_fw_mem_context(9)

---

mwah 💋 source/version ./drivers/gpu/drm/imagination, date October 2026, page pvr_vm_gpuva_unmap(9) — bye bestie, slay responsibly 🫶