Fix a deadlock with non-TSX and SPU creation #12617
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elad335
force-pushed
the
no-tsx-deadlock
branch
from
6c589c9
to
7fd54ab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
vm::writer_lock inside SPU constructor can lead to a deadlock when the waiting PPU waits for SPU to finish a lock-line update, but the SPU waits for a different PPU which hasn't unlocked its memory mutex because it is waiting on IDM mutex to unlock. (owned by the PPU creating the SPU)
Also, improve cellVdec performance with reservations. That is also where I've seen the second PPU deadlocks initially.