Base approximate time on a monotonic clock, like absolute time #320
Conversation
This file contains hidden or 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
MadCoder
suggested changes
Nov 13, 2017
src/shims/time.h
Outdated
| @@ -152,9 +152,9 @@ _dispatch_approximate_time(void) | |||
| struct timespec ts; | |||
| dispatch_assume_zero(clock_gettime(CLOCK_UPTIME_FAST, &ts)); | |||
| return _dispatch_timespec_to_nano(ts); | |||
| #elif defined(__linux__) | |||
| #elif HAVE_DECL_CLOCK_MONOTONIC_COARSE | |||
There was a problem hiding this comment.
please keep the if defined(__linux__) because CLOCK_MONOTONIC is supposed to tick during machine sleeps if you look at POSIX, and it happens to not be the case on linux which eventually became ABI on this platform.
However if a platform has (1) MONOTONIC_COARSE and not UPTIME_FAST, and (2) is POSIX compliant, then this would cause a bug for the said platform.
However you're right that MONOTONIC_COARSE is what we want here.
jblache
force-pushed
the
jblache/clock_monotonic
branch
from
c418375 to
700d08a
Compare
|
Amended; do we want to do the same in _dispatch_absolute_time() with a comment on top? |
|
we probably should now that you point this out. |
And document the reason behind this to avoid future bugs.
jblache
force-pushed
the
jblache/clock_monotonic
branch
from
700d08a to
58b23b8
Compare
|
How does that look? Ship it? |
ktopley-apple
pushed a commit
that referenced
this pull request
Dec 6, 2018
Base approximate time on a monotonic clock, like absolute time Signed-off-by: Daniel A. Steffen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caught this today; _dispatch_approximate_time() uses CLOCK_REALTIME on Linux for some reason, while _dispatch_absolute_time() uses CLOCK_MONOTONIC. This seems wrong and I can't think of a reason why this would be desirable in the first place.
Darwin code uses the same clock family for both, so use CLOCK_MONOTONIC_COARSE on Linux as the approximate time source, and test for it during configure.