Re: [RFC 0/6] drm/fences: add in-fences to DRM

From: Daniel Stone
Date: Thu Mar 31 2016 - 05:35:26 EST

Hi Inki,

On 31 March 2016 at 08:45, Inki Dae <inki.dae@xxxxxxxxxxx> wrote:
> 2016ë 03ì 29ì 22:23ì Rob Clark ì(ê) ì ê:
>> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae <inki.dae@xxxxxxxxxxx> wrote:
>>> In addition, I wonder how explicit and implicit fences could coexist together.
>>> Rob said,
>>> "Implicit sync ofc remains the default, but userspace could opt-in to explicit sync instead"
>>> This would mean that if we use explicit sync for user-space then it coexists with implicit sync. However, these two sync fences can't see same DMA buffer because explicit fence has a different file object from implicit one.
>>> So in this case, I think explicit fence would need to be hung up on the reservation object of dmabuf object somehow. Otherwise, although they coexist together, are these fences - explicit and implicit - used for differenct purpose separately?
>> I'm not entirely sure about coexistance at the same time. It ofc
>> shouldn't be a problem for one kernel to support both kinds of
>> userspace (pure explicit and pure implicit). And how this would work
>> on kms atomic ioctl (compositor/consumer) side seems clear enough..
>> ie. some sort of flag, which if set user provides an explicit fence
>> fd, and if not set we fall back to current behaviour (ie. get fences
>> from resv object).
> With this patch series, users can register explicit fence(s) to atomic kms(consumer side) through kms property interface for the explicit sync.
> However, now several DRM drivers(also consumer) already have beeen using implicit fence. So while GPU(producer side) is accessing DMA buffer after registering its explicit fence to atomic kms, and if atomic commit is requested by user-space, then atomic helper framework will try to synchronize with the producer - waiting for the signal of GPU side(producer), and device specific page flip function will also try to do same thing.

Well, it has to be one or the other: mixing explicit and implicit,
defeats the purpose of using explicit fencing. So, when explicit
fencing is in use, implicit fences must be ignored.

> As of now, it seems that this wouldn't be optional but mandatory if explicit fence support is added to the atomic helper framework. This would definitely be duplication and it seems not clear enough even if one of them is just skipped in runtime.

Drivers would have to opt in to explicit fencing support, and part of
that would be ensuring that the driver does not wait on implicit
fences when the user has requested explicit fencing be used.