Changes in drm_gpuvm.c

37f748ed0c19e007e7c5677f5d605d6b93841792 - drm/gpuvm: rust: add RUST_DRM_GPUVM option to Kconfig

Mon, 27 Apr 2026 12:54:51 +0200

drm/gpuvm: rust: add RUST_DRM_GPUVM option to KconfigSince Rust uses GPUVM via the kernel crate, which is built-in, the GPUVMmodule must also be built-in to use GPUVM from Rust. Adjust the Kconfigsettings accordingly.Suggested-by: Danilo Krummrich Signed-off-by: Alice Ryhl Link: https://patch.msgid.link/20260427-gpuvm-config-v1-1-8ece03771f8a@google.comSigned-off-by: Danilo Krummrich List of files: /linux/rust/helpers/drm_gpuvm.c

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/helpers/drm_gpuvm.c

82b78182eacf82c1847c6f1fd93d91c15efb69cf - rust: drm: add base GPUVM immediate mode abstraction

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

rust: drm: add base GPUVM immediate mode abstractionAdd a GPUVM abstraction to be used by Rust GPU drivers.GPUVM keeps track of a GPU's virtual address (VA) space and manages thecorresponding virtual mappings represented by "GPU VA" objects. It alsokeeps track of the gem::Object used to back the mappings throughGpuVmBo.This abstraction is only usable by drivers that wish to use GPUVM inimmediate mode. This allows us to build the locking scheme into the APIdesign. It means that the GEM mutex is used for the GEM gpuva list, andthat the resv lock is used for the extobj list. The evicted list is notyet used in this version.This abstraction provides a special handle called the UniqueRefGpuVm,which is a wrapper around ARef that provides access to theinterval tree. Generally, all changes to the address space requiresmutable access to this unique handle.Signed-off-by: Asahi Lina Co-developed-by: Daniel Almeida Signed-off-by: Daniel Almeida Reviewed-by: Daniel Almeida Co-developed-by: Alice Ryhl Signed-off-by: Alice Ryhl Link: https://patch.msgid.link/20260409-gpuvm-rust-v6-1-b16e6ada7261@google.comSigned-off-by: Danilo Krummrich List of files: /linux/rust/helpers/drm_gpuvm.c