[PATCH 0/2] drm/gpuvm+msm: Handle in-place remaps
Rob Clark
robin.clark at oss.qualcomm.com
Wed Jul 23 22:12:10 UTC 2025
turnip+msm uses a DUMP flag on the gpuva to indicate VA ranges to dump
(ie. for devcoredump). In most cases (internal BOs like shader
instructions) this is known at the time the BO is MAPd, and the DUMP
flag can be set at the same time as the BO is initially bound into the
VM. But for descriptor buffers, this isn't known until VkBuffer is
bound to the already mapped VkDeviceMemory, requiring an atomic remap
to set the flag.
The problem is that drmvm turns this into discreet unmap and remap
steps. So there is a window where the VA is not mapped, which can
race with cmdstream exec (SUBMIT).
This series attempts to avoid that by turning an exact-remap into a
remap op instead, where the driver can handle the special case since
it can see both the unmap and map steps at the same time.
Rob Clark (2):
drm/gpuvm: Send in-place re-maps to the driver as remap
drm/msm: Handle in-place remaps
drivers/gpu/drm/drm_gpuvm.c | 21 +++++++++++++++++++++
drivers/gpu/drm/msm/msm_gem_vma.c | 17 +++++++++++++++--
drivers/gpu/drm/nouveau/nouveau_uvmm.c | 3 ++-
3 files changed, 38 insertions(+), 3 deletions(-)
--
2.50.1
More information about the dri-devel
mailing list