linux-kernel - Re: perf sched replay again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 06 Jul 2012 15:30:37 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Dmitry Antipov <dmitry.antipov@...aro.org>
Cc:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org,
	patches@...aro.org
Subject: Re: perf sched replay again

Hi, Dmitry

On Wed, 04 Jul 2012 13:23:10 +0400, Dmitry Antipov wrote:
> I remember that this was rejected some time ago. Nevertheless,
> is it possible to accept this until we will have a better solution?
>

Why??? 

Ingo already merged da3789628f88 ("perf tools: Stop using a global
trace events description list"). Didn't it solve your problem?

On my tesing, it works well for cross-replay:

  $ ./perf sched -i ~/arm/perf.data replay
  run measurement overhead: 253 nsecs
  sleep measurement overhead: 55136 nsecs
  the run test took 1000013 nsecs
  the sleep test took 1057532 nsecs
  nr_run_events:        53
  nr_sleep_events:      62
  nr_wakeup_events:     31
  target-less wakeups:  1
  task      0 (           <unknown>:      1496), nr_events: 18
  task      1 (                perf:      1497), nr_events: 10
  task      2 (         ksoftirqd/0:         3), nr_events: 9
  task      3 (         kworker/0:1:       280), nr_events: 36
  task      4 (             swapper:         0), nr_events: 62
  task      5 (         sync_supers:       103), nr_events: 3
  task      6 (                init:         1), nr_events: 3
  task      7 (           flush-8:0:       560), nr_events: 3
  task      8 (            rsyslogd:      1135), nr_events: 3
  ------------------------------------------------------------
  #1  : 2664.545, ravg: 2664.54, cpu: 3125.45 / 3125.45
  #2  : 2664.978, ravg: 2664.59, cpu: 3124.99 / 3125.40
  #3  : 2664.736, ravg: 2664.60, cpu: 3125.68 / 3125.43
  #4  : 2664.620, ravg: 2664.60, cpu: 3125.96 / 3125.48
  #5  : 2665.132, ravg: 2664.66, cpu: 3126.02 / 3125.54
  #6  : 2665.096, ravg: 2664.70, cpu: 3083.47 / 3121.33
  #7  : 2665.585, ravg: 2664.79, cpu: 3125.66 / 3121.76
  #8  : 2664.839, ravg: 2664.79, cpu: 3126.01 / 3122.19
  #9  : 2664.750, ravg: 2664.79, cpu: 3125.38 / 3122.51
  #10 : 2668.297, ravg: 2665.14, cpu: 3116.82 / 3121.94
  
Of course, host and arm machine have different id's.

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/