Re: Perf record format portability

2012-05-31 Thread Dmitry Antipov
On 05/29/2012 07:10 PM, Arnaldo Carvalho de Melo wrote: I haven't tested this, but libtraceevent is now in, perhaps it works for you now? Can you check? It doesn't work. Attempt to do 'perf report' on ARM for the data collected on x86 shows 'unknown:unknown' for event names (see report_x86_on_

Re: Perf record format portability

2012-05-29 Thread Arnaldo Carvalho de Melo
Em Fri, May 18, 2012 at 09:48:26AM +0400, Dmitry Antipov escreveu: > On 05/17/2012 03:48 PM, Steven Rostedt wrote: > > >trace-cmd copies the entire /sys/kernel/debug/tracing/events directory > >into the data file (well it copies only the events you specify). > >I thought perf did the same. It shou

Re: Perf record format portability

2012-05-17 Thread Dmitry Antipov
On 05/17/2012 03:48 PM, Steven Rostedt wrote: trace-cmd copies the entire /sys/kernel/debug/tracing/events directory into the data file (well it copies only the events you specify). I thought perf did the same. It should be using what's in the perf.dat file and not what's on the host. I found

Re: Perf record format portability

2012-05-17 Thread Arnaldo Carvalho de Melo
Em Wed, May 16, 2012 at 12:58:23PM -0400, Steven Rostedt escreveu: > On Wed, 2012-05-16 at 11:59 -0300, Arnaldo Carvalho de Melo wrote: > > Was the kernel trace events infrastructure designed with that in > > mind? I.e. cross analysis? I must be missing something here, still > > ENOCOFFEE :-\ >

Re: Perf record format portability

2012-05-17 Thread Steven Rostedt
On Thu, 2012-05-17 at 09:10 +0400, Dmitry Antipov wrote: > On 05/16/2012 08:58 PM, Steven Rostedt wrote: > > > On Wed, 2012-05-16 at 11:59 -0300, Arnaldo Carvalho de Melo wrote: > > > >> Steve, > >> > >>Was the kernel trace events infrastructure designed with that in > >> mind? I.e. cross anal

Re: Perf record format portability

2012-05-17 Thread Steven Rostedt
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

Re: Perf record format portability

2012-05-17 Thread Steven Rostedt
On Wed, 2012-05-16 at 11:59 -0300, Arnaldo Carvalho de Melo wrote: > Steve, > > Was the kernel trace events infrastructure designed with that in > mind? I.e. cross analysis? I must be missing something here, still > ENOCOFFEE :-\ Yes, the libparsevents library was design for this from day

Re: Perf record format portability

2012-05-17 Thread Steven Rostedt
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!

Re: Perf record format portability

2012-05-17 Thread Steven Rostedt
On Wed, 2012-05-16 at 15:08 -0300, Arnaldo Carvalho de Melo wrote: > Em Wed, May 16, 2012 at 12:58:23PM -0400, Steven Rostedt escreveu: > > On Wed, 2012-05-16 at 11:59 -0300, Arnaldo Carvalho de Melo wrote: > > > Was the kernel trace events infrastructure designed with that in > > > mind? I.e. cr

Re: Perf record format portability

2012-05-17 Thread Jiri Olsa
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 tes

Re: Perf record format portability

2012-05-16 Thread Dmitry Antipov
On 05/16/2012 08:58 PM, Steven Rostedt wrote: On Wed, 2012-05-16 at 11:59 -0300, Arnaldo Carvalho de Melo wrote: Steve, Was the kernel trace events infrastructure designed with that in mind? I.e. cross analysis? I must be missing something here, still ENOCOFFEE :-\ Yes, the libparse

Re: Perf record format portability

2012-05-16 Thread Jiri Olsa
On Wed, May 16, 2012 at 12:58:23PM -0400, Steven Rostedt wrote: > On Wed, 2012-05-16 at 11:59 -0300, Arnaldo Carvalho de Melo wrote: > > > Steve, > > > > Was the kernel trace events infrastructure designed with that in > > mind? I.e. cross analysis? I must be missing something here, still > >

Re: Perf record format portability

2012-05-16 Thread Arnaldo Carvalho de Melo
Em Wed, May 16, 2012 at 05:16:55PM +0200, Jiri Olsa escreveu: > On Wed, May 16, 2012 at 11:59:27AM -0300, Arnaldo Carvalho de Melo wrote: > > Adding Jiri and Steven to the CC list. > > > > Em Wed, May 16, 2012 at 02:50:31PM +0400, Dmitry Antipov escreveu: > > > On 05/15/2012 07:51 PM, Arnaldo Carv

Re: Perf record format portability

2012-05-16 Thread Jiri Olsa
On Wed, May 16, 2012 at 11:59:27AM -0300, Arnaldo Carvalho de Melo wrote: > Adding Jiri and Steven to the CC list. > > Em Wed, May 16, 2012 at 02:50:31PM +0400, Dmitry Antipov escreveu: > > On 05/15/2012 07:51 PM, Arnaldo Carvalho de Melo wrote: > > >Em Tue, May 15, 2012 at 07:27:39PM +0400, Dmitr

Re: Perf record format portability

2012-05-16 Thread Arnaldo Carvalho de Melo
Adding Jiri and Steven to the CC list. Em Wed, May 16, 2012 at 02:50:31PM +0400, Dmitry Antipov escreveu: > On 05/15/2012 07:51 PM, Arnaldo Carvalho de Melo wrote: > >Em Tue, May 15, 2012 at 07:27:39PM +0400, Dmitry Antipov escreveu: > >>are there any thoughts on how much of the perf.data is porta

Re: Perf record format portability

2012-05-16 Thread Dmitry Antipov
On 05/15/2012 07:51 PM, Arnaldo Carvalho de Melo wrote: Em Tue, May 15, 2012 at 07:27:39PM +0400, Dmitry Antipov escreveu: Hello, are there any thoughts on how much of the perf.data is portable and how much it should be? I'm interesting in recording scheduler activity on one machine and then

Re: Perf record format portability

2012-05-15 Thread Arnaldo Carvalho de Melo
Em Tue, May 15, 2012 at 07:27:39PM +0400, Dmitry Antipov escreveu: > Hello, > > are there any thoughts on how much of the perf.data is portable and how much > it should be? > I'm interesting in recording scheduler activity on one machine and then > replaying on > another. As I can see, replaying