solo5: should not set booted_at to the new reboot time after a solo5_exec#1401
Merged
fwsGonzo merged 1 commit intoincludeos:devfrom Jun 29, 2017
Merged
Conversation
|
Can one of the admins verify this patch with one of the following commands:
|
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
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.
When doing a
solo5_execwe are resettinguptimeandmicros_since_boot. This is wrong asmicros_since_bootshould measure the time since the first boot (not the reboot due to the exec).This change fixes that by not setting the
booted_at_variable at every boot; instead, it leaves it at 0. This is a good approximation asbooted_at_usually has less than 1 ms (~700000 nanoseconds).@fwsGonzo ^^^