reuse_dmamap(9)
π reuse_dmamap(9) β the kernel API manual, bestie edition β¨
okay so you're in the Kernel API Manual and the page is reuse_dmamap(9) β yes the header says reuse_dmamap(9) on both sides, we love a symmetrical queen π
πΈ NAME πΈ
reuse_dmamap β literally just checks whether adev can share the original userptr BO π«Ά
π SYNOPSIS π
bool reuse_dmamap (struct amdgpu_device *adev , struct amdgpu_device
*bo_adev );
it's giving "tiny function, big responsibility" ngl π
π¦ ARGUMENTS π¦
adevβ the device that either can or cannot share the original BO, no in-between bestiebo_adevβ the device that the allocated BO actually belongs to π
π₯ DESCRIPTION π₯
so here's the vibe check: if both adev and bo_adev are in direct mapping, or they're in the same iommu group, then they can share the original BO. that's it, that's the whole lore β¨
β RETURN β
returns true if adev can share the original userptr BO, and false otherwise. binary icon behavior fr fr π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c amdgpu_amdkfd_reserve_mem_limit(9)create_dmamap_sg_bo(9)amdgpu_amdkfd_remove_all_eviction_fences(9)create_sg_table(9)kfd_mem_dmamap_sg_bo(9)kfd_mem_dmaunmap_sg_bo(9)reserve_bo_and_vm(9)reserve_bo_and_cond_vms(9)unreserve_bo_and_vms(9)amdgpu_amdkfd_gpuvm_pin_bo(9)amdgpu_amdkfd_gpuvm_unpin_bo(9)amdgpu_amdkfd_map_gtt_bo_to_gart(9)
like, go read them too, they're all in their main character era π
ok that's the whole page bestie, no cap, nothing skipped, every flag and function name preserved exactly π
and that's a wrap, mwah π β this little gem lives in ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it's part of the Kernel API Manual. slay, go forth and share those BOs responsibly πβ¨π¦
π¦ 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