<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [IGT] gem_ctx_thrash single test assertion failure on function gem_set_domain" href="https://bugs.freedesktop.org/show_bug.cgi?id=102936#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [IGT] gem_ctx_thrash single test assertion failure on function gem_set_domain" href="https://bugs.freedesktop.org/show_bug.cgi?id=102936">bug 102936</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Another contributing factor should be improved by: commit ca25fe5efe4ab43cc5b4f3117a205c281805a5ca Author: Christian König <<a href="mailto:ckoenig.leichtzumerken@gmail.com">ckoenig.leichtzumerken@gmail.com</a>> 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 <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>> Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Signed-off-by: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>> Link: <a href="https://patchwork.freedesktop.org/patch/msgid/20171114142436.1360-2-christian.koenig@amd.com">https://patchwork.freedesktop.org/patch/msgid/20171114142436.1360-2-christian.koenig@amd.com</a> commit 4d9c62e8ce69d0b0a834282a34bff5ce8eeacb1d Author: Christian König <<a href="mailto:ckoenig.leichtzumerken@gmail.com">ckoenig.leichtzumerken@gmail.com</a>> 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 <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>> Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Tested-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Signed-off-by: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>> Link: <a href="https://patchwork.freedesktop.org/patch/msgid/20171114142436.1360-1-christian.koenig@amd.com">https://patchwork.freedesktop.org/patch/msgid/20171114142436.1360-1-christian.koenig@amd.com</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>