On 06/29/2012 05:12 PM, Ingo Molnar wrote:
Pulled, thanks Arnaldo!
As of ca24a145573124732152daff105ba68cc9a2b545, 'perf sched replay' is still broken (but 'perf report' works) if perf.data was recorded on another machine. For example, native replay is:
run measurement overhead: 0 nsecs sleep measurement overhead: 112071 nsecs the run test took 1007080 nsecs the sleep test took 1159668 nsecs nr_run_events: 141 nr_sleep_events: 147 nr_wakeup_events: 73 target-less wakeups: 25 multi-target wakeups: 2 task 0 ( <unknown>: 4645), nr_events: 4 task 1 ( perf: 4646), nr_events: 190 task 2 ( swapper/1: 0), nr_events: 33 task 3 ( kworker/1:1: 20), nr_events: 126 task 4 ( sshd: 1881), nr_events: 32 task 5 ( kswapd0: 388), nr_events: 3 ------------------------------------------------------------ #1 : 29.663, ravg: 29.66, cpu: 54.38 / 54.38 #2 : 28.442, ravg: 29.54, cpu: 53.38 / 54.28 #3 : 28.564, ravg: 29.44, cpu: 54.02 / 54.26 #4 : 28.290, ravg: 29.33, cpu: 53.50 / 54.18 #5 : 29.877, ravg: 29.38, cpu: 53.16 / 54.08 #6 : 32.227, ravg: 29.67, cpu: 53.74 / 54.04 #7 : 27.588, ravg: 29.46, cpu: 52.67 / 53.91 #8 : 30.762, ravg: 29.59, cpu: 53.44 / 53.86 #9 : 28.381, ravg: 29.47, cpu: 53.04 / 53.78 #10 : 28.473, ravg: 29.37, cpu: 53.71 / 53.77
"Cross-replaying" of the same perf.data is:
run measurement overhead: 65 nsecs sleep measurement overhead: 55825 nsecs the run test took 1000140 nsecs the sleep test took 1064293 nsecs nr_run_events: 0 nr_sleep_events: 0 nr_wakeup_events: 0 ------------------------------------------------------------ #1 : 0.007, ravg: 0.01, cpu: 0.00 / 0.00 #2 : 0.001, ravg: 0.01, cpu: 0.00 / 0.00 #3 : 0.001, ravg: 0.01, cpu: 0.00 / 0.00 #4 : 0.001, ravg: 0.01, cpu: 0.00 / 0.00 #5 : 0.001, ravg: 0.01, cpu: 0.00 / 0.00 #6 : 0.001, ravg: 0.00, cpu: 0.00 / 0.00 #7 : 0.001, ravg: 0.00, cpu: 0.00 / 0.00 #8 : 0.001, ravg: 0.00, cpu: 0.00 / 0.00 #9 : 0.001, ravg: 0.00, cpu: 0.00 / 0.00 #10 : 0.001, ravg: 0.00, cpu: 0.00 / 0.00
Dmitry