From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Steven Rostedt <rostedt@goodmis.org>
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,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: Perf record format portability
Date: Wed, 16 May 2012 15:08:30 -0300 [thread overview]
Message-ID: <20120516180830.GH7864@infradead.org> (raw)
In-Reply-To: <1337187503.6724.50.camel@gandalf.stny.rr.com>
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 :-\
>
> Yes, the libparsevents library was design for this from day one. That's
> why trace-cmd data file can be run on an ARM and read on x86, or PPC, or
> whatever. I did all my development testing against 32bit, 64bit and big
> and little endian. This was the case from the beginning.
I need to look at the code, but how does it do this? Copy the relevant
/sys/kernel/debug/events formats in the header and then instead of
looking at /sys/... look at those?
Does it still copy /proc/kallsyms?
- Arnaldo
next prev parent reply other threads:[~2012-05-16 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 15:27 Perf record format portability 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
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 [this message]
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=20120516180830.GH7864@infradead.org \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=amit.kucheria@linaro.org \
--cc=dmitry.antipov@linaro.org \
--cc=jolsa@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.