Fix conditions for determining whether an event is included #11
+3
−2
Conversation
This file contains 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
zeroalphat
force-pushed
the
fix-cpu-event
branch
from
a883eb0
to
280ce79
Compare
Signed-off-by: zeroalphat <taichi-takemura@cybozu.co.jp>
zeroalphat
force-pushed
the
fix-cpu-event
branch
from
280ce79
to
94620db
Compare
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.
Until now, after executing perf record, necoperf checked whether the cpu-clock event was included in the perf.data file to confirm that the sample was acquired correctly.
However, when perf record was executed on the actual device, cycles events were recorded in the perf.data file instead of cpu-clock events, and necoperf could not correctly determine whether the sample was acquired.
To correct this bug, I changed the condition in the part that checks if the event is included.