-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simpleperf error when more than 6 events #1235
Comments
Hi, Thanks for reporting this. I suspect this means that your device only has 6 hardware counters available. When enabling more events than counters available I'm seeing additional messages in the raw
These messages are causing the parsing to fail so handling this scenario need to be fixed, however to prevent reduced accuracy I'd suggest limiting the number of events enabled if possible. |
Hmmmm, I think my device does allow 6 counters at the same time + the cycle counter which is 0x11 and can always be measured outside of the six. Is there any way I can just force the parse despite the limit? Or is that something that needs to be figured out on the simpleperf binary end? |
Although simpleperf can handle this, the main issue with the parsing is that these error messages are being printed in the middle of the output data which is the part of the reason the parsing is falling over. As a quick workaround we can try skipping the corrupted lines but this will mean that some entries will be dropped so we'll need to find a proper solution to this. In case it helps you I have pushed the workaround to my branch which can be found here [1] |
Hi, so I'm using the simpleperf stat command on WA, but when I have 7 events, there seems to be an error in the parsing stage. Only occurs when --csv is in the option string.
Here's the return error:
Couldn't quite figure out what the issue is. The moment I only have 6 events, it works just fine.
Thanks!
The text was updated successfully, but these errors were encountered: