Lines Matching refs:checkpoint

109 Suspension and checkpoint API
121 that runs a checkpoint function on behalf of each thread, either by using
161 lowest-level lock can always progress. An attempt to initiate a checkpoint or to
169 Running a checkpoint in a thread requires suspending that thread for the
170 duration of the checkpoint, or running the checkpoint on the threads behalf
172 checkpoint code is run from `CheckSuspend`, which requires the mutator lock,
173 so checkpoint code may only acquire mutexes at or below level
176 No matter whether the checkpoint is run in the target thread, or on its behalf,
180 checkpoint code should only acquire mutexes at level `kPostMonitorLock` or
204 the GC. Non-GC checkpoint or suspend requests that target a thread waiting on
209 situation in which the GC needs to suspend or checkpoint W2 by briefly stopping
213 suspend or execute a nonempty checkpoint. If we replaced the stop-the-world
214 phase by a checkpoint, W2 could receive the checkpoint request too late, and be
219 checkpoint request notifies the condition variable used to wait for reference
315     appropriate `ThreadFlag` entry to request suspension or a checkpoint. Note
316     that the actual checkpoint function value is set, along with the flag, while
318     checkpoint is requested, it then acquires the `suspend_count_lock_` to read
319     the checkpoint function.