duration_time regression
With recent perf duration_time output regressed:
e.g. with an older version I get duration_time only once:
% perf stat -e cycles,duration_time true
CPU0 190,925 cycles
... all the other CPUs printing cycles
CPU0 5,047,008 ns duration_time
0.005047008 seconds time elapsed
with the current perf it is printed on all CPUs, but not counted on most of them:
% perf stat -e cycles,duration_time true
# started on Tue Aug 1 13:29:26 2023
Performance counter stats for 'system wide':
CPU0 61,301 cycles
... print cycles for all CPUS ...
CPU0 5,343,556 ns duration_time CPU1 <not counted> ns duration_time CPU2 <not counted> ns duration_time CPU3 <not counted> ns duration_time CPU4 <not counted> ns duration_time
... repeat the same for all CPUs ...
which is fairly useless.
-Andi
Quoted 26 lines · Andi Kleen
With recent perf
duration_timeoutput regressed:e.g. with an older version I get
duration_timeonly once:% perf stat -e cycles,duration_time true
CPU0 190,925 cycles
... all the other CPUs printing cycles
CPU0 5,047,008 nsduration_time0.005047008 seconds time elapsedwith the current perf it is printed on all CPUs, but not counted on most of them:
% perf stat -e cycles,duration_time true
# started on Tue Aug 1 13:29:26 2023Performance counter stats for 'system wide':
CPU0 61,301 cycles
... print cycles for all CPUS ...
Quoted 8 lines
CPU0 5,343,556 ns duration_time CPU1 <not counted> ns duration_time CPU2 <not counted> ns duration_time CPU3 <not counted> ns duration_time CPU4 <not counted> ns duration_time... repeat the same for all CPUs ...
which is fairly useless.
Agreed, I sent out:
https://lore.kernel.org/lkml/[email protected]/
Thanks,
Ian
Quoted 1 line
-Andi