Changes in vm_bo.rs

dc3846045f694eef0606697e2304099cba403691 - rust: gpuvm: add GpuVmCore::sm_unmap()

Thu, 09 Apr 2026 17:26:09 +0200

rust: gpuvm: add GpuVmCore::sm_unmap()Add the entrypoint for unmapping ranges in the GPUVM, and providecallbacks and VA types for the implementation.Co-developed-by: Asahi Lina Signed-off-by: Asahi Lina Reviewed-by: Daniel Almeida Signed-off-by: Alice Ryhl Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-4-b16e6ada7261@google.comSigned-off-by: Danilo Krummrich List of files: /linux/rust/kernel/drm/gpuvm/vm_bo.rs

5540a9c747b3e1914ae68ae89f71c0a779bee5d1 - rust: gpuvm: add GpuVa struct

Thu, 09 Apr 2026 17:26:08 +0200

rust: gpuvm: add GpuVa structThis struct will be used to keep track of individual mapped ranges inthe GPU's virtual memory.Sparse VAs are not yet supported.Co-developed-by: Asahi Lina Signed-off-by: Asahi Lina Co-developed-by: Daniel Almeida Signed-off-by: Daniel Almeida Reviewed-by: Daniel Almeida Signed-off-by: Alice Ryhl Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-3-b16e6ada7261@google.comSigned-off-by: Danilo Krummrich List of files: /linux/rust/kernel/drm/gpuvm/vm_bo.rs

71a3921111bd05298988fad1c58241db13384ea7 - rust: gpuvm: add GpuVm::obtain()

Thu, 09 Apr 2026 17:26:07 +0200

rust: gpuvm: add GpuVm::obtain()This provides a mechanism to create (or look up) VMBO instances, whichrepresent the mapping between GPUVM and GEM objects.The GpuVmBoRegistered type can be considered like ARef>,except that no way to increment the refcount is provided.The GpuVmBoAlloc type is more akin to a pre-allocated GpuVmBo, soit's not really a GpuVmBo yet. Its destructor could calldrm_gpuvm_bo_destroy_not_in_lists(), but as the type is currentlyprivate and never called anywhere, this perf optimization does not needto happen now.Pre-allocating and obtaining the gpuvm_bo object is exposed as a singlestep. This could theoretically be a problem if one wanted to calldrm_gpuvm_bo_obtain_prealloc() during the fence signalling criticalpath, but that's not a possibility because:1. Adding the BO to the extobj list requires the resv lock, so it cannot happen during the fence signalling critical path.2. obtain() requires that the BO is not in the extobj list, so obtain() must be called before adding the BO to the extobj list.Thus, drm_gpuvm_bo_obtain_prealloc() cannot be called during the fencesignalling critical path. (For extobjs at least.)Reviewed-by: Daniel Almeida Signed-off-by: Alice Ryhl Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-2-b16e6ada7261@google.comSigned-off-by: Danilo Krummrich List of files: /linux/rust/kernel/drm/gpuvm/vm_bo.rs