Lines Matching refs:checkpoint

105 Suspension and checkpoint API
117 that runs a checkpoint function on behalf of each thread, either by using
157 lowest-level lock can always progress. An attempt to initiate a checkpoint or to
165 Running a checkpoint in a thread requires suspending that thread for the
166 duration of the checkpoint, or running the checkpoint on the threads behalf
168 checkpoint code is run from `CheckSuspend`, which requires the mutator lock,
169 so checkpoint code may only acquire mutexes at or below level
172 No matter whether the checkpoint is run in the target thread, or on its behalf,
176 checkpoint code should only acquire mutexes at level `kPostMonitorLock` or
200 the GC. Non-GC checkpoint or suspend requests that target a thread waiting on
205 situation in which the GC needs to suspend or checkpoint W2 by briefly stopping
209 suspend or execute a nonempty checkpoint. If we replaced the stop-the-world
210 phase by a checkpoint, W2 could receive the checkpoint request too late, and be
215 checkpoint request notifies the condition variable used to wait for reference
226 request suspension or a checkpoint. Note that the actual checkpoint function
228 target thread notices that a checkpoint is requested, it then acquires
229 the `suspend_count_lock_` to read the checkpoint function.