| commit | 99eeaab909ead3fb40d6a195bfa430a162fe4116 | |
| author | Aleksey Kliger <alklig@microsoft.com> | |
| Fri, 4 Jan 2019 16:41:10 +0000 (4 11:41 -0500) | ||
| committer | Aleksey Kliger (λgeek) <akliger@gmail.com> | |
| Wed, 9 Jan 2019 15:43:19 +0000 (9 10:43 -0500) | ||
| tree | e316dc88f395818e27ca4141a59fc40724b7a43a | treesnapshot (tar.gz zip) |
| parent | a19f9d869dd151bc394fda478533d22ed6674a9e | commitdiff |
[coop] Drop support for MONO_ENABLE_BLOCKING_TRANSITION env var
It was never documented and it is not as useful now with a matured hybrid
suspend.
If MONO_ENABLE_BLOCKING_TRANSITION set, and mono is otherwise configured to use
preemptive suspend, the thread state machinery would perform RUNNING->BLOCKING
transitions (ie: MONO_ENTER_GC_SAFE and friends would be more than no-ops), but
still preemptively suspend every thread. This was useful for testing the
thread transitions separately from the coop suspend details.
It was never documented and it is not as useful now with a matured hybrid
suspend.
If MONO_ENABLE_BLOCKING_TRANSITION set, and mono is otherwise configured to use
preemptive suspend, the thread state machinery would perform RUNNING->BLOCKING
transitions (ie: MONO_ENTER_GC_SAFE and friends would be more than no-ops), but
still preemptively suspend every thread. This was useful for testing the
thread transitions separately from the coop suspend details.
| mono/utils/mono-threads-coop.c | diffblobblamehistory |