On Tue, Sep 14, 2021 at 10:53 PM Gerd Hoffmann <kraxel@redhat.com> wrote:

On Wed, Sep 08, 2021 at 06:37:13PM -0700, Gurchetan Singh wrote:
> The plumbing is all here to do this. Since we always use the
> default fence context when allocating a fence, this makes no
> functional difference.
>
> We can't process just the largest fence id anymore, since it's
> it's associated with different timelines. It's fine for fence_id
> 260 to signal before 259. As such, process each fence_id
> individually.

I guess you need to also update virtio_gpu_fence_event_process()
then? It currently has the strict ordering logic baked in ...

The update to virtio_gpu_fence_event_process was done as a preparation a few months back:

https://cgit.freedesktop.org/drm/drm-misc/commit/drivers/gpu/drm/virtio/virtgpu_fence.c?id=36549848ed27c22bb2ffd5d1468efc6505b05f97

take care,
Gerd

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org