profiler: check paranoia level after trying SwCpuClock #730
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
In some setups, like running in an EKS cluster, currently there's a false negative where the profiler exits before trying SwCpuClock because it sees that the `perf_event_paranoid` level is set to 2. However, if the binary has been given correct capability (CAP_PERFMON), the paranoia level doesn't really matter. This patch fixes it to only check the paranoia level and error if we fail to run with both Hardware and Software CPU Clock events. Signed-off-by: Abhinav Gyawali <22275402+abhizer@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In some setups, like running in an EKS cluster, currently there's a false negative where the profiler exits before trying SwCpuClock because it sees that the
perf_event_paranoidlevel is set to 2. However, if the binary has been given correct capability (CAP_PERFMON), the paranoia level doesn't really matter.This patch fixes it to only check the paranoia level and error if we fail to run with both Hardware and Software CPU Clock events.