[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1336390149-2970-1-git-send-email-jolsa@redhat.com>
Date: Mon, 7 May 2012 13:29:04 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: acme@...hat.com, a.p.zijlstra@...llo.nl, mingo@...e.hu,
paulus@...ba.org, cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com
Cc: linux-kernel@...r.kernel.org, dsahern@...il.com,
Caspar Zhang <czhang@...hat.com>
Subject: [PATCHv3 0/5] perf, tool: Fix endian issues
hi,
sending fixies to properly handle perf.data endians.
v3 changes:
- added patch 5 to fix addons bitmask handling
v2 changes:
- added patches 3 and 4 to handle sample_id_all header endianity
Attached patches:
1/5 perf, tool: Handle different endians properly during symbol load
2/5 perf, tool: Carry perf_event_attr bitfield throught different endians
3/5 perf, tool: Handle endianity swap on sample_id_all header data
4/5 perf, tool: Fix 32 bit values endianity swap for sample_id_all header
5/5 perf, tool: Fix endianity trick for adds_features bitmask
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
Big thank to Caspar Zhang who verified this within RH QE testsuites.
thanks,
jirka
CC: Caspar Zhang <czhang@...hat.com>
---
tools/perf/util/evsel.c | 32 ++++++++--
tools/perf/util/header.c | 20 +++++--
tools/perf/util/include/linux/bitops.h | 1 +
tools/perf/util/session.c | 101 ++++++++++++++++++++++++++++----
tools/perf/util/symbol.c | 33 ++++++++++-
tools/perf/util/symbol.h | 30 +++++++++
6 files changed, 192 insertions(+), 25 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists