search for: drm_gpuvm_sm_map_repeat

...44,10 +2346,43 @@ drm_gpuvm_sm_map(struct drm_gpuvm *gpuvm, void *priv, return __drm_gpuvm_sm_map(gpuvm, ops, priv, req_addr, req_range, - req_obj, req_offset); + req_obj, req_offset, 0); } EXPORT_SYMBOL_GPL(drm_gpuvm_sm_map); +/** + * drm_gpuvm_sm_map_repeat() - repeatedly maps a GEM range over a VA range + * @gpuvm: the &drm_gpuvm representing the GPU VA space + * @priv: pointer to a driver private data structure + * @req_addr: the start address of the new mapping + * @req_range: the range of the new mapping + * @req_obj: the &drm_gem_object t...

Hi Lina, On Sun, Feb 02, 2025 at 10:34:49PM +0900, Asahi Lina wrote: > Some hardware requires dummy page mappings to efficiently implement > Vulkan sparse features. These mappings consist of the same physical > memory page, repeated for a large range of address space (e.g. 16GiB). > > Add support for this to drm_gpuvm. Currently, drm_gpuvm expects BO > ranges to correspond 1:1

...m *gpuvm, void *priv, > > return __drm_gpuvm_sm_map(gpuvm, ops, priv, > req_addr, req_range, > - req_obj, req_offset); > + req_obj, req_offset, 0); > } > EXPORT_SYMBOL_GPL(drm_gpuvm_sm_map); > > +/** > + * drm_gpuvm_sm_map_repeat() - repeatedly maps a GEM range over a VA range > + * @gpuvm: the &drm_gpuvm representing the GPU VA space > + * @priv: pointer to a driver private data structure > + * @req_addr: the start address of the new mapping > + * @req_range: the range of the new mapping > + * @req_obj:...