https://bugs.freedesktop.org/show_bug.cgi?id=107403
--- Comment #1 from Christian König ckoenig.leichtzumerken@gmail.com --- Well that should be already fixed by the following commits:
commit ca25fe5efe4ab43cc5b4f3117a205c281805a5ca Author: Christian König ckoenig.leichtzumerken@gmail.com Date: Tue Nov 14 15:24:36 2017 +0100
dma-buf: try to replace a signaled fence in reservation_object_add_shared_inplace
The amdgpu issue to also need signaled fences in the reservation objects should be fixed by now.
Optimize the handling by replacing a signaled fence when adding a new shared one.
Signed-off-by: Christian König christian.koenig@amd.com Reviewed-by: Chris Wilson chris@chris-wilson.co.uk Signed-off-by: Alex Deucher alexander.deucher@amd.com Link: https://patchwork.freedesktop.org/patch/msgid/20171114142436.1360-2-christia...
commit 4d9c62e8ce69d0b0a834282a34bff5ce8eeacb1d Author: Christian König ckoenig.leichtzumerken@gmail.com Date: Tue Nov 14 15:24:35 2017 +0100
dma-buf: keep only not signaled fence in reservation_object_add_shared_replace v3
The amdgpu issue to also need signaled fences in the reservation objects should be fixed by now.
Optimize the list by keeping only the not signaled yet fences around.
v2: temporary put the signaled fences at the end of the new container v3: put the old fence at the end of the new container as well.
Signed-off-by: Christian König christian.koenig@amd.com Reviewed-by: Chris Wilson chris@chris-wilson.co.uk Tested-by: Chris Wilson chris@chris-wilson.co.uk Signed-off-by: Alex Deucher alexander.deucher@amd.com Link: https://patchwork.freedesktop.org/patch/msgid/20171114142436.1360-1-christia...