When CL-GL interop is used, a GL context are used by two or more threads at the same time, which causes race condition.
Solution:
Add lock when accessing GL functions during CL-GL interop.
Change-Id: I3a34da3cbdf74c401111cc4e3a04ad84cc52709e
[ROCm/clr commit: 0c6a952a90]
- Create a vector to allow multiple TS to be stored in Command.
- This would mean we dont wait for entire batch in Accumulate command
to finish when we exhaust signals.
- Reduce the number of signals created at init to 64. This min value
may still need to be tuned but the KFD allows max of 4094 interrupt
signals per device.
- Store kernel names whenever they are available and not just when
profiling. If we dynamically enable profiling like for Torch, a crash
can happen if hipGraphInstantiate wasnt included in Torch profile scope
beacuse we previously entered kernel names only when profiler is
attached.
Change-Id: I34e7881a25bbc763f82fdeb3408a8ea58e1ec006
[ROCm/clr commit: c157bfb202]
Modifies the behavior of clEnqueueAcquireGLObjects and
clEnqueueReleaseGLObjects to implicitly guarantee synchronization
with an OpenGL context bound in the same thread as
the OpenCL context.
Change-Id: I23eddee37a77f6c1c9d1a9ad3a3e1eb254a1ed82
[ROCm/clr commit: c4cde09339]
Danylo Lytovchenko
Gu, Wangfeng
Saleel Kudchadker
victzhan
agunashe
Vladislav Sytchenko
German Andryeyev
Laurent Morichetti