From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
paulus@samba.org, cjashfor@linux.vnet.ibm.com,
fweisbec@gmail.com, linux-kernel@vger.kernel.org,
Caspar Zhang <czhang@redhat.com>
Subject: Re: [PATCHv3 0/5] perf, tool: Fix endian issues
Date: Mon, 07 May 2012 21:49:17 -0600 [thread overview]
Message-ID: <4FA897BD.4000304@gmail.com> (raw)
In-Reply-To: <1336390149-2970-1-git-send-email-jolsa@redhat.com>
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.
Long answer to reproduce:
In the PPC VM:
1. build perf without your patches
2. perf record -ag -fo /tmp/perf.data -- sleep 1
In the host (x86_64) using the same code base:
1. build perf without your patches
2. mount ppc filesystem (e.g.,
sshfs root@172.16.128.67:/ /tmp/f12-ppc/ -o direct_io)
3. analyze ppc file. Verify life is good:
/tmp/jiri/perf script --symfs /tmp/f12-ppc \
-I -i /tmp/f12-ppc/tmp/perf.data \
--kallsyms /tmp/f12-ppc/proc/kallsyms
# ========
# captured on: Mon May 7 21:32:15 2012
# hostname : f12-ppc
# os release : 2.6.32.26-175.fc12.ppc
# perf version : 3.4.0-rc2
# arch : ppc
# nrcpus online : 1
# nrcpus avail : 1
# cpudesc : 740/750
# cpuid : 8,769
# total memory : 1024572 kB
# cmdline : /tmp/pbuild/perf record -ag -fo /tmp/perf.data -v -e
cpu-clock -- sleep 5
# event : name = cpu-clock, type = 1, config = 0x0, config1 = 0x0,
config2 = 0x0, excl_usr = 0, excl_kern = 0, id = { 6 }
# ========
#
...
Apply your patches and rebuild the host (x86_64 version). Life is not so
good:
/tmp/jiri/perf script --symfs /tmp/f12-ppc \
-I -i /tmp/f12-ppc/tmp/perf.data \
--kallsyms /tmp/f12-ppc/proc/kallsyms
# ========
# captured on: Mon May 7 21:32:15 2012
# ========
#
i.e, all the feature data has gone missing.
David
next prev parent reply other threads:[~2012-05-08 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 11:29 [PATCHv3 0/5] perf, tool: Fix endian issues Jiri Olsa
2012-05-07 11:29 ` [PATCH 1/5] perf, tool: Handle different endians properly during symbol load Jiri Olsa
2012-05-07 11:29 ` [PATCH 2/5] perf, tool: Carry perf_event_attr bitfield throught different endians Jiri Olsa
2012-05-07 11:29 ` [PATCH 3/5] perf, tool: Handle endianity swap on sample_id_all header data Jiri Olsa
2012-05-07 11:29 ` [PATCH 4/5] perf, tool: Fix 32 bit values endianity swap for sample_id_all header Jiri Olsa
2012-05-07 11:29 ` [PATCH 5/5] perf, tool: Fix endianity trick for adds_features bitmask Jiri Olsa
2012-05-07 16:15 ` David Ahern
2012-05-08 2:12 ` [PATCHv3 0/5] perf, tool: Fix endian issues David Ahern
2012-05-08 3:37 ` David Ahern
2012-05-08 3:49 ` David Ahern [this message]
2012-05-10 10:38 ` Jiri Olsa
2012-05-10 16:30 ` Jiri Olsa
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=4FA897BD.4000304@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=czhang@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.