| 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
| ||
|
Message-ID: <1337197154.6724.68.camel@gandalf.stny.rr.com> Date: Wed, 16 May 2012 15:39:14 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Jiri Olsa <jolsa@...hat.com> Cc: Arnaldo Carvalho de Melo <acme@...stprotocols.net>, Dmitry Antipov <dmitry.antipov@...aro.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...hat.com>, Amit Kucheria <amit.kucheria@...aro.org>, linaro-dev@...ts.linaro.org, linux-kernel@...r.kernel.org Subject: Re: Perf record format portability 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@...p-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? -- Steve -- 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/
Powered by blists - more mailing lists