Re: [PATCH v3 2/2] drm/virtio: New fence for every plane update

2024-10-25 Thread Dmitry Osipenko
On 10/22/24 07:44, Kasireddy, Vivek wrote: >> virtio_gpu_cmd_resource_flush(vgdev, bo->hw_res_handle, >> x, y, >> - width, height, objs, vgfb->fence); >> + width, height, objs, >> +

RE: [PATCH v3 2/2] drm/virtio: New fence for every plane update

2024-10-21 Thread Kasireddy, Vivek
Hi Dmitry, > Subject: [PATCH v3 2/2] drm/virtio: New fence for every plane update > > From: Dongwon Kim > > 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.

[PATCH v3 2/2] drm/virtio: New fence for every plane update

2024-10-20 Thread Dmitry Osipenko
From: Dongwon Kim 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