APIs that take KernelTimeout as a parameter can now query if an absolute or relative timeout was requested. If the underlying API can only use one type of timeout, the code will do a reasonable conversion. The goal is to eventually enable the possibility of using wait times that are based on monotonic clocks that are safe against system clock steps. PiperOrigin-RevId: 508541507 Change-Id: Id08bf13515f3e1bfd78d88393cde98a6fd3ef72c
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| internal | Loading commit data... | |
| BUILD.bazel | Loading commit data... | |
| CMakeLists.txt | Loading commit data... | |
| barrier.cc | Loading commit data... | |
| barrier.h | Loading commit data... | |
| barrier_test.cc | Loading commit data... | |
| blocking_counter.cc | Loading commit data... | |
| blocking_counter.h | Loading commit data... | |
| blocking_counter_benchmark.cc | Loading commit data... | |
| blocking_counter_test.cc | Loading commit data... | |
| lifetime_test.cc | Loading commit data... | |
| mutex.cc | Loading commit data... | |
| mutex.h | Loading commit data... | |
| mutex_benchmark.cc | Loading commit data... | |
| mutex_method_pointer_test.cc | Loading commit data... | |
| mutex_test.cc | Loading commit data... | |
| notification.cc | Loading commit data... | |
| notification.h | Loading commit data... | |
| notification_test.cc | Loading commit data... |