[BUG] perf tests: Test converting perf time to TSC

[Jiri Olsa]

hi,
got a segfault in the tsc test on latest acme's tree.

I'm dealing with some other issues right now, so just reporting ;-)

thanks,
jirka

(gdb) r test 20
Starting program: /home/jolsa/linux-perf/tools/perf/perf test 20
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
20: Test converting perf time to TSC                       :
Program received signal SIGFPE, Arithmetic exception.
0x00000000004cee73 in perf_time_to_tsc (ns=1460625577603, tc=0x7fffffffdf50) at arch/x86/util/tsc.c:16
16              quot = t / tc->time_mult;
Missing separate debuginfos, use: debuginfo-install audit-libs-2.2.1-1.fc16.x86_64 elfutils-libelf-0.154-2.fc16.x86_64 elfutils-libs-0.154-2.fc16.x86_64 glibc-2.14.90-24.fc16.9.x86_64 nss-softokn-freebl-3.14.1-3.fc16.x86_64 numactl-2.0.7-2.fc16.x86_64 perl-libs-5.14.3-205.fc16.x86_64 python-libs-2.7.3-4.fc16.x86_64 slang-2.2.4-1.fc16.x86_64 xz-libs-5.1.1-1alpha.fc16.x86_64 zlib-1.2.5-7.fc16.x86_64
(gdb) bt
#0  0x00000000004cee73 in perf_time_to_tsc (ns=1460625577603, tc=0x7fffffffdf50) at arch/x86/util/tsc.c:16
#1  0x00000000004cbdb8 in test__perf_time_to_tsc () at tests/perf-time-to-tsc.c:144
#2  0x00000000004491b7 in __cmd_test (argc=1, argv=0x7fffffffe400, skiplist=0x0) at tests/builtin-test.c:175
#3  0x0000000000449512 in cmd_test (argc=1, argv=0x7fffffffe400, prefix=0x0) at tests/builtin-test.c:240
#4  0x0000000000418dfd in run_builtin (p=0x802500, argc=2, argv=0x7fffffffe400) at perf.c:319
#5  0x0000000000419035 in handle_internal_command (argc=2, argv=0x7fffffffe400) at perf.c:376
#6  0x0000000000419181 in run_argv (argcp=0x7fffffffe2dc, argv=0x7fffffffe2d0) at perf.c:420
#7  0x0000000000419468 in main (argc=2, argv=0x7fffffffe400) at perf.c:529
(gdb) p tc->time_mult
$1 = 0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/