search for: virtgpu_execbuf_flag

Displaying 5 results from an estimated 5 matches for "virtgpu_execbuf_flag".

Did you mean: virtgpu_execbuf_flags
2018 Nov 02
0
[PATCH 2/5] drm/virtio: add uapi for in and out explicit fences
...f->fence_fd = -1; > >> + > > Move this after the sanity checking. > > Agreed. Fixed in v4 > > > > >> if (vgdev->has_virgl_3d == false) > >> return -ENOSYS; > >> > >> + if ((exbuf->flags & ~VIRTGPU_EXECBUF_FLAGS)) > >> + return -EINVAL; > >> + > > I assume this did this trigger when using old userspace? > > No, not as far as I'm aware. This check is there to prevent userspace from > polluting the bitspace of flag, so that all free bits can be used for new...
2023 Mar 22
0
[PATCH v2 1/2] drm/virtio: Refactor job submission code path
...truct drm_virtgpu_execbuffer *exbuf = data; > + struct virtio_gpu_submit submit; > + uint32_t ring_idx = 0; > + int ret = -EINVAL; > + > + if (vgdev->has_virgl_3d == false) > + return -ENOSYS; > + > + if ((exbuf->flags & ~VIRTGPU_EXECBUF_FLAGS)) > + return ret; > + > + if ((exbuf->flags & VIRTGPU_EXECBUF_RING_IDX)) { > + if (exbuf->ring_idx >= vfpriv->num_rings) > + return ret; > + > + if (!vfpriv->base_fence_ctx) > +...
2020 Apr 07
0
[vhost:vhost 32/44] drivers/gpu/drm/virtio/virtgpu_ioctl.c:113:7: error: implicit declaration of function 'copy_from_user'; did you mean 'sg_copy_from_buffer'?
...n 2014-10-28 68 62fb7a5e10962a Gerd Hoffmann 2014-10-28 69 if (vgdev->has_virgl_3d == false) 62fb7a5e10962a Gerd Hoffmann 2014-10-28 70 return -ENOSYS; 62fb7a5e10962a Gerd Hoffmann 2014-10-28 71 a56f9c868ccf56 Robert Foss 2018-11-12 72 if ((exbuf->flags & ~VIRTGPU_EXECBUF_FLAGS)) a56f9c868ccf56 Robert Foss 2018-11-12 73 return -EINVAL; a56f9c868ccf56 Robert Foss 2018-11-12 74 a56f9c868ccf56 Robert Foss 2018-11-12 75 exbuf->fence_fd = -1; a56f9c868ccf56 Robert Foss 2018-11-12 76 2cd7b6f08bc4cf Robert Foss 2018-11-12 77 if (exbuf...
2016 Dec 12
6
[RFC 1/5] drm/virtio: add virtio_gpu_alloc_fence()
From: Gustavo Padovan <gustavo.padovan at collabora.co.uk> Refactor fence creation to remove the potential allocation failure from the cmd_submit and atomic_commit paths. Now the fence should be allocated first and just after we should proceed with the rest of the execution. Signed-off-by: Gustavo Padovan <gustavo.padovan at collabora.co.uk> --- drivers/gpu/drm/virtio/virtgpu_drv.h
2016 Dec 12
6
[RFC 1/5] drm/virtio: add virtio_gpu_alloc_fence()
From: Gustavo Padovan <gustavo.padovan at collabora.co.uk> Refactor fence creation to remove the potential allocation failure from the cmd_submit and atomic_commit paths. Now the fence should be allocated first and just after we should proceed with the rest of the execution. Signed-off-by: Gustavo Padovan <gustavo.padovan at collabora.co.uk> --- drivers/gpu/drm/virtio/virtgpu_drv.h