the problem with that approach is that it duplicates the effort done
with android fences but moves some of the logic found in there into the
E.g. you could do the same with in/out fences on command submission,
just not share the handle itself with other process before it is
signaled (which is actually desirable).
Am 01.12.2016 um 07:11 schrieb zhoucm1:
As the attached, our Vulkan team is verifying it.
On 2016年12月01日 13:44, Dave Airlie wrote:
On 1 Dec. 2016 15:22, "zhoucm1" <david1.z...@amd.com
> Yes, the old implementation which is already in upstream libdrm is
out of data, there isn't other user, so we want to drop it when new
semaphore is verified OK.
Could you post some patches for the new one? Otherwise I'll have to
write one for radv.
> David Zhou
> On 2016年12月01日 10:36, Mao, David wrote:
>> Hi Dave,
>> i believe your first attempt is correct.
>> The export/import semaphore needs refine of the semaphore
>> We are working on that.
>> Best Regards,
>>> On 1 Dec 2016, at 10:12 AM, Dave Airlie <airl...@gmail.com
>>> Hey all,
>>> So I've started adding semaphore support to radv but I'm not really
>>> sure what the API to the semaphore code is.
>>> the Vulkan API is you get a command submission of a number of submit
>>> units which have a 0-n wait semaphore, 0-n command buffers and 0-n
>>> signal semaphores.
>>> Now I'm not sure how I should use the APIs with those.
>>> My first attempt is
>>> call amdgpu_cs_wait_semaphore on all the wait ones, call the cs
>>> API, then call the amdgpu_cs_signal_semaphore on all the signal ones?
>>> or should I be up front calling wait/signal then submitting the
>>> Also upcoming work requires possibly sharing semaphores between
>>> processes, is there any indication how this might be made work with
>>> the libdrm_amdgpu semaphore implementation?
>>> amd-gfx mailing list
>>> email@example.com <mailto:firstname.lastname@example.org>
>> amd-gfx mailing list
>> email@example.com <mailto:firstname.lastname@example.org>
amd-gfx mailing list
amd-gfx mailing list