You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found some code that confused me in Configure multiple counters Section under Use perf_event_open for counting Chapter.
In the code under the annotation // Read the group of counters and print result, it shows like this...
We can see that traverse id[j] here is to check the true_id that value belonged to. However, it assign the value with index i to pe_val with this same index i (not j) and print them sequentially. It make the check part useless.
So, is there any problem around here ?
The text was updated successfully, but these errors were encountered:
Yes, you can get rid of that inner for loop and check. I don't recall exactly why I placed that check there. I was probably paranoid about something and wanted to make sure the data returned in the counters_results was actually indexed the same way as when the events were created.
I found some code that confused me in Configure multiple counters Section under Use perf_event_open for counting Chapter.
In the code under the annotation
// Read the group of counters and print result
, it shows like this...We can see that traverse id[j] here is to check the true_id that value belonged to. However, it assign the
value
with indexi
tope_val
with this same indexi
(notj
) and print them sequentially. It make the check part useless.So, is there any problem around here ?
The text was updated successfully, but these errors were encountered: