Messages in this thread |  | | | Date | Thu, 10 May 2012 18:30:33 +0200 | | From | Jiri Olsa <> | | Subject | Re: [PATCHv3 0/5] perf, tool: Fix endian issues |
| |
On Thu, May 10, 2012 at 12:38:25PM +0200, Jiri Olsa wrote: > On Mon, May 07, 2012 at 09:49:17PM -0600, David Ahern wrote: > > On 5/7/12 5:29 AM, Jiri Olsa wrote: > > >Tested by running following usecase: > > > - origin system: > > > # perf record -a -- sleep 10 (any perf record will do) > > > # perf report> report.origin > > > # perf archive perf.data > > > > > > - copy the perf.data, report.origin and perf.data.tar.bz2 > > > to a target system and run: > > > # tar xjvf perf.data.tar.bz2 -C ~/.debug > > > # perf report> report.target > > > # diff -u report.origin report.target > > > > > > - the diff should produce no output > > > (besides some white space stuff and possibly different > > > date/TZ output) > > > > > >Tested by above usecase cross following architectures: > > > i386, x86_64, s390x, ppc64 > > > > Short answer: Now that I have perf compiling in a 32-bit PPC VM, > > applied the patchset and rebuilding -- it does not work for me. > > hi, > Could I ask what VM did you use? My qemu setup does not seem > to offer this one. > > so it's [32 bits big endian] into [64 bits small endian] > > I tested i386 to ppc64. The endianity is the other way round, > I wonder whats wrong with your tested direction. > > hunting testing machine ;)
reproduced ;) working on fix
jirka
|  |