Re: [PATCH] drm/virtio: add missing virtio_gpu_array_lock_resv call

2020-01-10 Thread Chia-I Wu
On Fri, Jan 10, 2020 at 6:27 AM Jann Horn wrote: > > On Fri, Jan 10, 2020 at 10:45 AM Gerd Hoffmann wrote: > > When submitting a fenced command we must lock the object reservations > > because virtio_gpu_queue_fenced_ctrl_buffer() unlocks after adding the > > fence. > > Thanks a lot! With this pa

Re: [PATCH] drm/virtio: add missing virtio_gpu_array_lock_resv call

2020-01-10 Thread Jann Horn via Virtualization
On Fri, Jan 10, 2020 at 10:45 AM Gerd Hoffmann wrote: > When submitting a fenced command we must lock the object reservations > because virtio_gpu_queue_fenced_ctrl_buffer() unlocks after adding the > fence. Thanks a lot! With this patch applied, my VM doesn't throw lockdep warnings anymore. If y

[PATCH] drm/virtio: add missing virtio_gpu_array_lock_resv call

2020-01-10 Thread Gerd Hoffmann
When submitting a fenced command we must lock the object reservations because virtio_gpu_queue_fenced_ctrl_buffer() unlocks after adding the fence. Reported-by: Jann Horn Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_plane.c | 1 + 1 file changed, 1 insertion(+) diff --git a/