mirror of
https://github.com/torvalds/linux.git
synced 2026-09-22 20:54:03 +02:00
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>
This commit is contained in:
parent
c4c4434e41
commit
49d0307c55
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user