From: Christopher James Halse Rogers
Migration to VRAM will break the sharing, resulting in rendering on the
exporting GPU never becoming
visible on the importing GPU.
v2: Don't pin BOs to GTT. Instead, refuse to migrate them out of GTT.
Signed-off-by: Christopher James Halse Rogers
---
dri
From: Christopher James Halse Rogers
Signed-off-by: Christopher James Halse Rogers
---
drivers/gpu/drm/radeon/radeon.h | 1 +
drivers/gpu/drm/radeon/radeon_prime.c | 6 ++
2 files changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/radeon/radeon.h b/drivers/gpu/drm/radeon/radeon.h
From: Christopher James Halse Rogers
BOs shared via dma-buf, either imported or exported, cannot sensibly be
migrated to VRAM
without breaking the dma-buf sharing. Refuse userspace requests to migrate to
VRAM,
ensure such BOs are not migrated during command submission, and refuse to pin
them
t
From: Christopher James Halse Rogers
Attempting to migrate the bo will break the sharing of the buffer.
v2: Error-check the nouveau_bo_pin call; it can fail.
Signed-off-by: Christopher James Halse Rogers
---
drivers/gpu/drm/nouveau/nouveau_prime.c | 6 ++
1 file changed, 6 insertions(+)
From: Christopher James Halse Rogers
CC: intel-...@lists.freedesktop.org
Signed-off-by: Christopher James Halse Rogers
---
drivers/gpu/drm/i915/i915_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
inde
My past set of patches fix nouveau, radeon, and amdgpu breaking dma-buf sharing
when
trying to scanout of an imported PRIME buffer. Driver-agnostic userspace can't
safely
try to scanout of such a buffer, though, because the failure-mode is that
subsequent
rendering isn't shown on screen.
This a
From: Christopher James Halse Rogers
Until recently, on (at least) nouveau, radeon, and amdgpu attempting to scanout
of an
imported dma-buf would silently result in the dma-buf sharing being broken.
While the hardware is capable of scanning out of imported dma-bufs (at least in
some circumstan
For nouveau, radeon, and amdgpu attempting to scanout of a bo will cause
the driver to migrate it to VRAM.
When the bo in question is an imported dma-buf, this results in a buffer
that appears to be shared but is actually device-private.
Consensus on #dri-devel seemed to be that it would be appro
From: Christopher James Halse Rogers
Attempting to migrate the bo will break the sharing of the buffer.
Signed-off-by: Christopher James Halse Rogers
CC: amd-...@lists.freedesktop.org
---
drivers/gpu/drm/radeon/radeon_prime.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/dri
From: Christopher James Halse Rogers
Any use of the framebuffer will migrate it to VRAM, which is not sensible for
an imported dma-buf.
Signed-off-by: Christopher James Halse Rogers
CC: amd-...@lists.freedesktop.org
---
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 6 ++
1 file changed, 6
From: Christopher James Halse Rogers
Any use of the framebuffer will migrate it to VRAM, which is not sensible for
an imported dma-buf.
Signed-off-by: Christopher James Halse Rogers
CC: nouv...@lists.freedesktop.org
---
drivers/gpu/drm/nouveau/nouveau_display.c | 4
1 file changed, 4 ins
From: Christopher James Halse Rogers
Attempting to migrate the bo will break the sharing of the buffer.
Signed-off-by: Christopher James Halse Rogers
CC: amd-...@lists.freedesktop.org
---
drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
From: Christopher James Halse Rogers
Any use of the framebuffer will migrate it to VRAM, which is not sensible for
an imported dma-buf.
Signed-off-by: Christopher James Halse Rogers
CC: amd-...@lists.freedesktop.org
---
drivers/gpu/drm/radeon/radeon_display.c | 6 ++
1 file changed, 6 ins
From: Christopher James Halse Rogers
Attempting to migrate the bo will break the sharing of the buffer.
Signed-off-by: Christopher James Halse Rogers
CC: nouv...@lists.freedesktop.org
---
drivers/gpu/drm/nouveau/nouveau_prime.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu
From: Christopher James Halse Rogers
Any use of the framebuffer will migrate it to VRAM, which is not sensible for
an imported dma-buf.
v2: Use DRM_DEBUG_KMS to prevent userspace accidentally spamming dmesg.
Signed-off-by: Christopher James Halse Rogers
CC: amd-...@lists.freedesktop.org
---
From: Christopher James Halse Rogers
Any use of the framebuffer will migrate it to VRAM, which is not sensible for
an imported dma-buf.
v2: Use DRM_DEBUG_KMS to prevent userspace accidentally spamming dmesg.
Signed-off-by: Christopher James Halse Rogers
CC: amd-...@lists.freedesktop.org
---
16 matches
Mail list logo
