We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accordingly to https://stackoverflow.com/questions/3523442/difference-between-clock-realtime-and-clock-monotonic, CLOCK_REALTIME is related to system time and may even jumps backward, while CLOCK_MONOTONIC is related to time passed since boot and cannot go back.
CLOCK_REALTIME
CLOCK_MONOTONIC
Given this definition, query_performance_counter() is using wrong clock source.
query_performance_counter()
The text was updated successfully, but these errors were encountered:
Fix #7649 - Switch Linux performance counter timer to CLOCK_MONOTONIC…
0055687
…_RAW.
dddfcf4
…_RAW. (#7650)
asfernandes
Successfully merging a pull request may close this issue.
Accordingly to https://stackoverflow.com/questions/3523442/difference-between-clock-realtime-and-clock-monotonic,
CLOCK_REALTIME
is related to system time and may even jumps backward, whileCLOCK_MONOTONIC
is related to time passed since boot and cannot go back.Given this definition,
query_performance_counter()
is using wrong clock source.The text was updated successfully, but these errors were encountered: