summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorAdrián Larumbe <adrian.larumbe@collabora.com>2026-06-08 23:33:53 +0100
committerDanilo Krummrich <dakr@kernel.org>2026-07-03 23:32:55 +0200
commit49d0307c55c4f713bf9515e6ef52ed0942cea27d (patch)
tree260b333392e36dc53ea0b65c9f1254eddd991903 /include
parentc4c4434e41e5875b1c922e4c5783466687e75c76 (diff)
drm/gpuvm: Fix comment to reflect remap operation operand status
When a new mapping intersects with an existing GPU VA, but either end lies before or beyond the existing VA's edges, then the prev and next mapping operations part of a remap will reflect this condition by being set to NULL. Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com> Link: https://patch.msgid.link/20260608-gpuvm-minor-fixes-v2-2-af07ef9ca969@collabora.com Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'include')
-rw-r--r--include/drm/drm_gpuvm.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/drm/drm_gpuvm.h b/include/drm/drm_gpuvm.h
index f8fc0296c4b7..38221d83285b 100644
--- a/include/drm/drm_gpuvm.h
+++ b/include/drm/drm_gpuvm.h
@@ -928,6 +928,8 @@ struct drm_gpuva_op_unmap {
* If either a new mapping's start address is aligned with the start address
* of the old mapping or the new mapping's end address is aligned with the
* end address of the old mapping, either @prev or @next is NULL.
+ * This will also be the case when the requested mapping begins before the
+ * old mapping's start address or stretches beyond its end address.
*
* Note, the reason for a dedicated remap operation, rather than arbitrary
* unmap and map operations, is to give drivers the chance of extracting driver