pvr_vm_gpuva_map(9)
β¨ NAME β¨
okay bestie, welcome to pvr_vm_gpuva_map(9) from the Kernel API Manual π this one literally just inserts a mapping into a memory context, and it's giving "small function, important job" energy.
π SYNOPSIS π
int pvr_vm_gpuva_map (struct drm_gpuva_op *op , void *op_ctx );
π ARGUMENTS π
opβ the gpuva op carrying the remap details β¨op_ctxβ the operation context π«Ά
π§ CONTEXT π§
so this gets called by drm_gpuvm_sm_map after a mapping succeeds, while the op_ctx.vm_ctx mutex is held π. that's the context, bestie β no cap.
π₯ RETURN π₯
0on success, or- any error returned by
pvr_mmu_map.
π SEE ALSO π
go read these too, iykyk π:
- 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_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_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)
bye bestie π
this page came from ./drivers/gpu/drm/imagination, dated October 2026, and yes β it's still pvr_vm_gpuva_map(9) π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms