jfr: set the clock setting to the actual rather than attempted clock #1141
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
Before this PR, the clock setting in the JFR contains which clock we attempted to use. This changes it to contain the actual clock used, so if there was a failed attempt to use the tsc clock, it will say "monotonic".
krk
pushed a commit
to krk/async-profiler
that referenced
this pull request
Mar 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Before this PR, the clock setting in the JFR contains which clock we attempted to use. This changes it to contain the actual clock used, so if there was a failed attempt to use the tsc clock, it will say "monotonic".
How has this been tested?
Tested locally to do the right thing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.