[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c06c005d-41a8-5403-818b-f66264fe8c0b@collabora.com>
Date: Mon, 6 Feb 2023 20:20:46 +0300
From: Dmitry Osipenko <dmitry.osipenko@...labora.com>
To: Ryan Neph <ryanneph@...omium.org>,
David Airlie <airlied@...hat.com>,
Gerd Hoffmann <kraxel@...hat.com>,
Daniel Vetter <daniel@...ll.ch>,
Gurchetan Singh <gurchetansingh@...omium.org>,
Chia-I Wu <olvaffe@...il.com>, dri-devel@...ts.freedesktop.org,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Cc: Yiwei Zhang <zzyiwei@...omium.org>,
Rob Clark <robdclark@...omium.org>,
Rob Clark <robdclark@...il.com>,
Emil Velikov <emil.velikov@...labora.com>,
Gustavo Padovan <gustavo.padovan@...labora.com>
Subject: Re: [PATCH v2] drm/virtio: exbuf->fence_fd unmodified on interrupted
wait
On 2/4/23 02:33, Ryan Neph wrote:
> An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned
> to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to
> retry the ioctl(), but the passed exbuf->fence_fd has been reset to -1,
> making the retry attempt fail at sync_file_get_fence().
>
> The uapi for DRM_IOCTL_VIRTGPU_EXECBUFFER is changed to retain the
> passed value for exbuf->fence_fd when returning anything besides a
> successful result from the ioctl.
>
> Fixes: 2cd7b6f08bc4 ("drm/virtio: add in/out fence support for explicit synchronization")
> Signed-off-by: Ryan Neph <ryanneph@...omium.org>
> Reviewed-by: Rob Clark <robdclark@...il.com>
> Reviewed-by: Dmitry Osipenko <dmitry.osipenko@...labora.com>
>
> ---
>
> Changes in v2:
> - No longer modifies exbuf->fence_fd unless DRM_IOCTL_VIRTGPU_EXECBUFFER
> succeeds.
> - Added r-b tags (Rob/Dmitry) from v1.
Thanks! Applied to misc-fixes
--
Best regards,
Dmitry
Powered by blists - more mailing lists