Skip to content

Conversation

@hjelmn
Copy link
Member

@hjelmn hjelmn commented Jan 12, 2017

The linux timer code was multiplying the result of the x86 time stamp
counter by 1000000 before dividing by the cpu frequency. This can
cause us to overflow 64 bits if the time stamp counter grows larger
than ~ 1.8e13 (about 8400 seconds after boot). To fix the issue the
units of opal_timer_linux_freq have been changed to MHz.

Signed-off-by: Nathan Hjelm hjelmn@lanl.gov
(cherry picked from commit 45c0588)
Signed-off-by: Nathan Hjelm hjelmn@lanl.gov

The linux timer code was multiplying the result of the x86 time stamp
counter by 1000000 before dividing by the cpu frequency. This can
cause us to overflow 64 bits if the time stamp counter grows larger
than ~ 1.8e13 (about 8400 seconds after boot). To fix the issue the
units of opal_timer_linux_freq have been changed to MHz.

Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
(cherry picked from commit 45c0588)
Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
@hjelmn hjelmn added this to the v1.10.6 milestone Jan 12, 2017
@hjelmn hjelmn requested a review from bosilca January 12, 2017 17:05
Copy link
Member

@jsquyres jsquyres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hjelmn @bosilca There's no backwards compatibility issues here, right? I.e., the scale/units returned to the user are still the same, right?

@rhc54
Copy link
Contributor

rhc54 commented Jan 17, 2017

bot:mellanox:retest

@rhc54 rhc54 merged commit 88c2708 into open-mpi:v1.10 Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants