Commit 9f065194 authored by Yang Shi's avatar Yang Shi Committed by Arnaldo Carvalho de Melo

perf record: Change 'record.samples' type to unsigned long long

When run "perf record -e", the number of samples showed up is wrong on some
32 bit systems, i.e. powerpc and arm.

For example, run the below commands on 32 bit powerpc:

  perf probe -x /lib/libc.so.6 malloc
  perf record -e probe_libc:malloc -a ls perf.data
  [ perf record: Woken up 1 times to write data ]
  [ perf record: Captured and wrote 0.036 MB perf.data (13829241621624967218 samples) ]

Actually, "perf script" just shows 21 samples. The number of samples is also
absurd since samples is long type, but it is printed as PRIu64.

Build test ran on x86-64, x86, aarch64, arm, mips, ppc and ppc64.
Signed-off-by: default avatarYang Shi <yang.shi@linaro.org>
Cc: linaro-kernel@lists.linaro.org
Link: http://lkml.kernel.org/r/1443563383-4064-1-git-send-email-yang.shi@linaro.org
[ Bumped the 'hits' var used together with record.samples to 'unsigned long long' too ]
Signed-off-by: default avatarArnaldo Carvalho de Melo <acme@redhat.com>
parent 1a8ac29c
...@@ -49,7 +49,7 @@ struct record { ...@@ -49,7 +49,7 @@ struct record {
int realtime_prio; int realtime_prio;
bool no_buildid; bool no_buildid;
bool no_buildid_cache; bool no_buildid_cache;
long samples; unsigned long long samples;
}; };
static int record__write(struct record *rec, void *bf, size_t size) static int record__write(struct record *rec, void *bf, size_t size)
...@@ -667,7 +667,7 @@ static int __cmd_record(struct record *rec, int argc, const char **argv) ...@@ -667,7 +667,7 @@ static int __cmd_record(struct record *rec, int argc, const char **argv)
auxtrace_snapshot_enabled = 1; auxtrace_snapshot_enabled = 1;
for (;;) { for (;;) {
int hits = rec->samples; unsigned long long hits = rec->samples;
if (record__mmap_read_all(rec) < 0) { if (record__mmap_read_all(rec) < 0) {
auxtrace_snapshot_enabled = 0; auxtrace_snapshot_enabled = 0;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment