pvr_vm_unmap_obj(9)

💖 NAME 💖

okay so bestie, this is the pvr_vm_unmap_obj(9) page from the Kernel API Manual — manual name folded in right at the top, we love a tidy entrance ✨. This function is literally here to unmap an already mapped section of device-virtual memory. That's the whole vibe. 💅

🦋 SYNOPSIS 🦋

the signature, untouched and iconic — copy it exactly, no improvising:

int pvr_vm_unmap_obj (struct pvr_vm_context *vm_ctx , struct
       pvr_gem_object *pvr_obj , u64 device_addr , u64 size );

🌸 ARGUMENTS 🌸

• vm_ctx — target VM context. like, the VM context we're doing this to 🎀
• pvr_obj — target PowerVR memory object. the object in question, bestie.
• device_addr — virtual device address at the start of the target mapping. so the starting address of the mapping we're targeting.
• size — size of the target mapping. how big the target mapping is, periodt.

🔥 RETURN 🔥

• 0 on success 🫶
• Any error encountered by pvr_vm_unmap_obj_locked.

👑 SEE ALSO 👑

Kernel file ./drivers/gpu/drm/imagination/pvr_vm.c — hi source file bestie 🌈

• 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_unmap(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(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)

and that's the whole page, bestie 🫶 — source/version is ./drivers/gpu/drm/imagination, dated October 2026, and the manual name for the sign-off is pvr_vm_unmap_obj(9). slay ✨💜