Re: [PATCH 1/5] drm/virtio: add virtio_gpu_alloc_fence()

> > On Thu, 25 Oct 2018 at 19:38, Robert Foss wrote: > > > > > > From: Gustavo Padovan > > > > > > 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

Re: [PATCH 1/5] drm/virtio: add virtio_gpu_alloc_fence()

Hey Emil, On 2018-10-31 10:38, Emil Velikov wrote: Hi Rob, On Thu, 25 Oct 2018 at 19:38, Robert Foss wrote: From: Gustavo Padovan 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

Re: [PATCH 1/5] drm/virtio: add virtio_gpu_alloc_fence()

Hi Rob, On Thu, 25 Oct 2018 at 19:38, Robert Foss wrote: > > From: Gustavo Padovan > > 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

[PATCH 1/5] drm/virtio: add virtio_gpu_alloc_fence()

From: Gustavo Padovan 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 Signed-off-by: Robert Fos