My first email can be ignored except for the sync files. Oh well.
I think I see what you mean, Christian. If we assume that an imported fence
is always read only (the buffer with the sequence number is read only),
only the process that created and exported the fence can signal it. If the
fence is
If both implicit and explicit synchronization are handled the same, then
the kernel won't be able to identify the process that caused an implicit
sync deadlock. The process that is stuck waiting for a fence can be
innocent, and the kernel can't punish it. Likewise, the GPU reset guery
that reports
Hi Marek,
well I don't think that implicit and explicit synchronization needs to
be mutual exclusive.
What we should do is to have the ability to transport an synchronization
object with each BO.
Implicit and explicit synchronization then basically become the same,
they just transport the
