forked from Pissandshittium/pissandshittium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Mojo: Properly assert sync call restrictions
For off-thread sync IPC waits on [NoInterrupt] messages, we were intentionally not asserting sync call restrictions. Instead we rely on the implicit assertion that base sync primitives are allowed. This was done due to the fact that some important GPU sync IPCs are sent during thread teardown (not process shutdown) in renderers, and asserting sync call restrictions relies on sequence-local storage which may already be torn down by the time it's needed. Ideally callers would not need to know about the distinction though, and they should be able to rely on ScopedAllowSyncCall for all cases. This CL addresses the issue by making Mojo's sync call restriction state management and assertion operations silently do nothing when sequence-local storage is no valid for the calling thread. Bug: 1196476 Change-Id: I24c2a726662ba0b18faa2fb3b97f33e13422f854 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2856822 Reviewed-by: François Doray <fdoray@chromium.org> Reviewed-by: Zhenyao Mo <zmo@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Auto-Submit: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#877506}
- Loading branch information
Showing
5 changed files
with
33 additions
and
3 deletions.
There are no files selected for viewing
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
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
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
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
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