| Issue |
64681
|
| Summary |
[libomptarget] potential deadlock in amdgpu plugin
|
| Labels |
new issue
|
| Assignees |
jdoerfert,
kevinsala
|
| Reporter |
ye-luo
|
Tries to guess why https://github.com/llvm/llvm-project/issues/64572 happens.
In a threaded code,
T1 gets Stream 1 and summit Event 1
T2 gets Stream 2 and summit Event 2
T3 gets Stream 3 and summit Event 3
now for what ever reason each thread picks up the next stream
T1 gets Stream 2 and summit Event 1. Tries to lock stream 1 and 2
T2 gets Stream 3 and summit Event 2. Tries to lock stream 2 and 3
T3 gets Stream 1 and summit Event 3. Tries to lock stream 3 and 1
at https://github.com/llvm/llvm-project/blob/e63382542f0941b550839a226d0e2ad02a9de328/openmp/libomptarget/plugins-nextgen/amdgpu/src/rtl.cpp#L1436
I feel deadlock may happen and we need to avoid actively waiting a stream through its recorded stream.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
