15 Sep
2021
15 Sep
'21
5:53 a.m.
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 ...
take care, Gerd