[lkml]   [2019]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v6 15/18] drm/virtio: rework virtio_gpu_transfer_to_host_ioctl fencing
> > > ... 3d case passes the objs list to virtio_gpu_cmd_transfer_to_host_3d,
> > > so it gets added to the vbuf and released when the command is finished.
> > Why doesn't this apply to virtio_gpu_cmd_transfer_to_host_2d?
> Hmm, yes, makes sense to handle both the same way.
> With virgl=off qemu processes the commands from the guest
> synchronously, so it'll work fine as-is. So you can't hit
> the theoretical race window in practice. But depending
> on that host-side implementation detail isn't a good idea
> indeed.

Branch with incremental fixes:

I'll be offline three weeks now, will resume this when I'm back.


 \ /
  Last update: 2019-07-05 16:08    [W:0.041 / U:1.772 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site