From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Dmitry Antipov <dmitry.antipov@linaro.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Amit Kucheria <amit.kucheria@linaro.org>,
linaro-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Perf record format portability
Date: Wed, 16 May 2012 17:16:55 +0200 [thread overview]
Message-ID: <20120516151655.GE1820@m.brq.redhat.com> (raw)
In-Reply-To: <20120516145927.GC7864@infradead.org>
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, Dmitry Antipov escreveu:
> > >>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 x86 perf.data on ARM doesn't work. At least, should it
> > >>work with a small subset of recorded events (for example, sched:sched_switch,
> > >>sched:sched_process_exit, sched:sched_process_fork, sched:sched_wakeup
> > >>and sched:sched_migrate_task) on the same architecture?
> > >
> > >Endianness issues? ARM EB? There are some patches by Jiri Olsa that may
> > >help you if that is the case.
latest version sent today, there's description of tests I did:
http://marc.info/?l=linux-kernel&m=133715172512742&w=2
Each time I run new sort of test, another endianity issue is hit.
so, tracepoints.. I'll check ;)
jirka
next prev parent reply other threads:[~2012-05-16 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 15:27 Dmitry Antipov
2012-05-15 15:51 ` Arnaldo Carvalho de Melo
2012-05-16 10:50 ` Dmitry Antipov
2012-05-16 14:59 ` Arnaldo Carvalho de Melo
2012-05-16 15:16 ` Jiri Olsa [this message]
2012-05-16 15:50 ` Arnaldo Carvalho de Melo
2012-05-16 16:58 ` Steven Rostedt
2012-05-16 17:48 ` Jiri Olsa
2012-05-16 19:32 ` Steven Rostedt
2012-05-16 19:39 ` Steven Rostedt
2012-05-17 8:51 ` Jiri Olsa
2012-05-16 18:08 ` Arnaldo Carvalho de Melo
2012-05-16 18:17 ` Steven Rostedt
2012-05-17 5:10 ` Dmitry Antipov
2012-05-17 11:48 ` Steven Rostedt
2012-05-18 5:48 ` Dmitry Antipov
2012-05-29 15:10 ` Arnaldo Carvalho de Melo
2012-05-31 8:28 ` Dmitry Antipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120516151655.GE1820@m.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=amit.kucheria@linaro.org \
--cc=dmitry.antipov@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome