public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Antipov <dmitry.antipov@linaro.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Amit Kucheria <amit.kucheria@linaro.org>,
	linaro-dev@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Perf record format portability
Date: Tue, 15 May 2012 19:27:39 +0400	[thread overview]
Message-ID: <4FB275EB.5050904@linaro.org> (raw)

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 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?

Thanks in advance,
Dmitry

             reply	other threads:[~2012-05-15 15:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 15:27 Dmitry Antipov [this message]
2012-05-15 15:51 ` Perf record format portability 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
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=4FB275EB.5050904@linaro.org \
    --to=dmitry.antipov@linaro.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=amit.kucheria@linaro.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.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