This repository was archived by the owner on Jun 23, 2026. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comment would help. It seems calling 'wait()' is equivalent to holding
qmutexandwait_no_lock()which is what is lines 4185 below after lockingrocrQueuesMutex. Does this fix imply thatrocrQueuesMutexshould NOT be held beforeqmutexas it may cause deadlock? If so, shouldn't line 4185 locking ofqmutexbe removed?Or, could moving acquiring of
rocrQueuesMutexto just before callingremoveRocrQueue()help?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait_no_lock()could potentially callEnqueueMarkerNoLock(). If theHSAQueuedoes not hold a rocr queue, it will end up callingcreateOrstealRocrQueue()and lockrocrQueuesMutex.Moving the lock on
rocrQueuesMutexuntil just before line 4206 might work, too.