linux.git/drivers/gpu/drm/virtio/virtgpu_plane.c, branch v6.16

drm/virtio: Support drm_panic with non-vmapped shmem BO

2025-04-16T07:19:42+00:00

Pass array of pages of the scanout buffer to shmem BO, allowing
drm_panic to work even if the BO is not vmapped.

Link: https://lore.kernel.org/all/20250407140138.162383-3-jfalempe@redhat.com/
Signed-off-by: Jocelyn Falempe 
Signed-off-by: Ryosuke Yasuoka 
Reviewed-by: Dmitry Osipenko 
Tested-by: Dmitry Osipenko 
Signed-off-by: Dmitry Osipenko 
[dmitry.osipenko@collabora.com: rebased on misc-next, fixed minor checkpatch warn]
[dmitry.osipenko@collabora.com: changed commit message to use link tag]
Link: https://lore.kernel.org/all/20250412132012.291837-1-ryasuoka@redhat.com/

drm/virtio: Test for imported buffers with drm_gem_is_imported()

2025-04-16T07:05:03+00:00

Instead of testing import_attach for imported GEM buffers, invoke
drm_gem_is_imported() to do the test. The helper tests the dma_buf
itself while import_attach is just an artifact of the import. Prepares
to make import_attach optional.

Signed-off-by: Thomas Zimmermann 
Reviewed-by: Dmitry Osipenko 
Signed-off-by: Dmitry Osipenko 
Link: https://lore.kernel.org/r/20250414131507.566072-2-tzimmermann@suse.de

Merge drm/drm-fixes into drm-misc-fixes

2025-04-08T08:15:47+00:00

Backmerging to get updates from v6.15-rc1.

Signed-off-by: Thomas Zimmermann

drm/virtio: Fix missed dmabuf unpinning in error path of prepare_fb()

2025-04-01T20:11:55+00:00

Correct error handling in prepare_fb() to fix leaking resources when
error happens.

Fixes: 4a696a2ee646 ("drm/virtio: Add prepare and cleanup routines for imported dmabuf obj")
Cc:  # v6.14+
Acked-by: Vivek Kasireddy 
Signed-off-by: Dmitry Osipenko 
Link: https://lore.kernel.org/r/20250401123842.2232205-2-dmitry.osipenko@collabora.com

drm/virtio: Add drm_panic support

2025-02-09T17:36:51+00:00

Virtio gpu supports the drm_panic module, which displays a message to
the screen when a kernel panic occurs. It is supported where it has
vmapped shmem BO.

Signed-off-by: Jocelyn Falempe 
Signed-off-by: Ryosuke Yasuoka 
Tested-by: Dmitry Osipenko 
Reviewed-by: Dmitry Osipenko 
Signed-off-by: Dmitry Osipenko 
Link: https://patchwork.freedesktop.org/patch/msgid/20250206104300.416014-1-ryasuoka@redhat.com

drm/virtio: Add prepare and cleanup routines for imported dmabuf obj

2024-11-26T10:28:02+00:00

When an imported dmabuf obj is used as part of an atomic commit, we
need to pin it as part of prepare and unpin it during cleanup of
the associated FB, to make sure that it does not move until the
commit is completed (and also while it is being used on the Host).

Cc: Gerd Hoffmann 
Cc: Dmitry Osipenko 
Cc: Rob Clark 
Cc: Gurchetan Singh 
Cc: Chia-I Wu 
Signed-off-by: Vivek Kasireddy 
Tested-by: Dmitry Osipenko 
Reviewed-by: Dmitry Osipenko 
Signed-off-by: Dmitry Osipenko 
Link: https://patchwork.freedesktop.org/patch/msgid/20241126031643.3490496-6-vivek.kasireddy@intel.com

drm/virtio: New fence for every plane update

2024-11-18T18:18:15+00:00

Having a fence linked to a virtio_gpu_framebuffer in the plane update
sequence would cause conflict when several planes referencing the same
framebuffer (e.g. Xorg screen covering multi-displays configured for an
extended mode) and those planes are updated concurrently. So it is needed
to allocate a fence for every plane state instead of the framebuffer.

Signed-off-by: Dongwon Kim 
[dmitry.osipenko@collabora.com: rebase, fix up, edit commit message]
Signed-off-by: Dmitry Osipenko 
Acked-by: Vivek Kasireddy 
Reviewed-by: Rob Clark 
Link: https://patchwork.freedesktop.org/patch/msgid/20241020230803.247419-2-dmitry.osipenko@collabora.com

drm/virtio: Use drm_gem_plane_helper_prepare_fb()

2024-11-18T18:18:13+00:00

Use drm_gem_plane_helper_prepare_fb() helper for explicit framebuffer
synchronization. We need to wait for explicit fences in a case of
Venus and native contexts when guest user space uses explicit fencing.

Signed-off-by: Dongwon Kim 
[dmitry.osipenko@collabora.com: edit commit message]
Signed-off-by: Dmitry Osipenko 
Acked-by: Vivek Kasireddy 
Reviewed-by: Rob Clark 
Link: https://patchwork.freedesktop.org/patch/msgid/20241020230803.247419-1-dmitry.osipenko@collabora.com

drm/virtio: Disable damage clipping if FB changed since last page-flip

2023-11-24T14:15:27+00:00

The driver does per-buffer uploads and needs to force a full plane update
if the plane's attached framebuffer has change since the last page-flip.

Fixes: 01f05940a9a7 ("drm/virtio: Enable fb damage clips property for the primary plane")
Cc:  # v6.4+
Reported-by: nerdopolis 
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218115
Suggested-by: Sima Vetter 
Signed-off-by: Javier Martinez Canillas 
Reviewed-by: Thomas Zimmermann 
Reviewed-by: Zack Rusin 
Acked-by: Sima Vetter 
Link: https://patchwork.freedesktop.org/patch/msgid/20231123221315.3579454-3-javierm@redhat.com

drm/virtio: Use the hotspot properties from cursor planes

2023-11-24T10:58:01+00:00

Atomic modesetting got support for mouse hotspots via the hotspot
properties. Port the legacy kms hotspot handling to the new properties
on cursor planes.

Signed-off-by: Zack Rusin 
Reviewed-by: Gerd Hoffmann 
Cc: David Airlie 
Cc: Gurchetan Singh 
Cc: Chia-I Wu 
Cc: Daniel Vetter 
Cc: virtualization@lists.linux-foundation.org
Reviewed-by: Javier Martinez Canillas 
Signed-off-by: Javier Martinez Canillas 
Link: https://patchwork.freedesktop.org/patch/msgid/20231023074613.41327-7-aesteve@redhat.com