<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 18/03/2019 17:20, Koenig, Christian wrote: </div> <blockquote type="cite" cite="mid:990db9e7-6cae-1165-637c-84aed3a9af49@amd.com"> <blockquote type="cite" style="color: #000000;"> <blockquote type="cite" style="color: #000000;"> <pre class="moz-quote-pre" wrap=""> - if (dma_fence_is_signaled(entries[i].fence)) { + if (fence) + entries[i].fence = fence; + else + entries[i].fence = dma_fence_get_stub(); + + if ((flags & DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE) || </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> Hey David, Could you remind me what DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE is used for? I didn't have a use for it in userspace, </pre> </blockquote> <pre class="moz-quote-pre" wrap="">The flag is used to wait for fences for a sequence number to show up. Christian. </pre> </blockquote> Thanks Christian. I guess I missed the additive nature of WAIT_FOR_SUBMIT. It feels like WAIT_AVAILABLE almost deserves its own commit as it affects both timelines & binary syncobjs. -Lionel </body> </html>