Hi Lionel, For binary semaphore, I guess every one will think application
will guarantee wait is behind the signal, whenever the semaphore
is shared or used in internal-process. I think below two options can fix your problem: a. Can we extend vkWaitForFence so that it can be able to wait on fence-available? If fence is available, then it's safe to do semaphore wait in vkQueueSubmit. b. Make waitBeforeSignal is valid for binary semaphore as well,
as that way, It is reasonable to add wait/signal counting for
binary syncobj.
-David On 2019年08月02日 14:27, Lionel Landwerlin
wrote:
|
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel