On Wed, May 16, 2012 at 03:39:14PM -0400, Steven Rostedt wrote:
On Wed, 2012-05-16 at 15:32 -0400, Steven Rostedt wrote:
On Wed, 2012-05-16 at 19:48 +0200, Jiri Olsa wrote:
for ppc64(record) vs x86_64(report) I got following report on latest tip:
[jolsa@dhcp-26-214 test]$ ../perf report > report.target Endianness of raw data not corrected! Warning: 718 samples with id not present in the header Warning: The perf.data file has no samples!
What does perf script give you. It looks like Frederic took my code for this when he ported the original parse-events over to perf. I see the setup of these variables in tools/perf/util/trace-event-read.c
If you run 'perf script' on x86 from a ppc perf.dat file, do you still get the same errors?
yes
--- [jolsa@dhcp-26-214 test]$ ../perf script Endianness of raw data not corrected! Warning: 718 samples with id not present in the header # ======== # captured on: Wed May 16 19:53:13 2012 # hostname : ibm-js22-vios-02-lp1.rhts.eng.bos.redhat.com # os release : 2.6.32-270.el6.ppc64 # perf version : 2.6.32-270.el6.ppc64.debug # arch : ppc64 # nrcpus online : 8 # nrcpus avail : 8 # cpudesc : POWER6 (architected), altivec supported # cpuid : 62,769 # total memory : 6236992 kB # cmdline : /usr/bin/perf record -a -e sched:sched_switch -e # sched:sched_process_exit -e sched:sched_process_fork -e # sched:sched_wakeup -- sleep 10 # event : name = sched:sched_switch, type = 2, config = 0x22, config1 = # 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0, id = { 97, 98, 99, # 100, 101, 102, 103, 104 } # event : name = sched:sched_process_exit, type = 2, config = 0x1b, # config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0, id = { 105, # 106, 107, 108, 109, 110, 111, 112 } # event : name = sched:sched_process_fork, type = 2, config = 0x1d, # config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0, id = { 113, # 114, 115, 116, 117, 118, 119, 120 } # event : name = sched:sched_wakeup, type = 2, config = 0x17, config1 = # 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0, id = { 121, 122, 123, # 124, 125, 126, 127, 128 } # HEADER_CPU_TOPOLOGY info available, use -I to display # HEADER_NUMA_TOPOLOGY info available, use -I to display # ======== # ---
jirka