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
Notice that IOC_RESET resets the value of the counter, but doesn't affect time_enabled or time_running
It's hard to say what the correct behavior is here, but this means that the Counter object is no longer valid because its running / enabled ratio is not what it thinks it is:
julia> stats
╶ cpu-cycles 0.00e+0076.3%# 0.0 cycles per ns
┌ cache-references 0.00e+0062.0%
└ cache-misses 0.00e+0062.0%# NaN% of cache refs
┌ branch-instructions 0.00e+0061.8%# NaN% of insns
│ branch-misses 0.00e+0061.8%# NaN% of branch insns
└ instructions 0.00e+0061.8%# NaN insns per cycle
┌ context-switches 0.00e+00100.0%
│ page-faults 0.00e+00100.0%
│ minor-faults 0.00e+00100.0%
│ major-faults 0.00e+00100.0%
└ cpu-migrations 0.00e+00100.0%
If you try to reset in a loop, this means you end up scaling the measurement by its average running time instead of its true running time for the latest sample.
The text was updated successfully, but these errors were encountered:
Looks like we can't change this behaviour and the package only uses it to reset the counter,
PERF_EVENT_IOC_RESET
Reset the event count specified by the file descriptor
argument to zero. This resets only the counts; there is
no way to reset the multiplexing time_enabled or
time_running values.
I am slightly concerned that we use this right after opening an event, does the counter not start at 0? If not, is the same true for the time running and time enabled fields.
Notice that
IOC_RESET
resets the value of the counter, but doesn't affecttime_enabled
ortime_running
It's hard to say what the correct behavior is here, but this means that the
Counter
object is no longer valid because its running / enabled ratio is not what it thinks it is:If you try to reset in a loop, this means you end up scaling the measurement by its average running time instead of its true running time for the latest sample.
The text was updated successfully, but these errors were encountered: