5630 2013-12-05 10:31:12 +0000 perf test shows multiple errors and fails on qemux86 2014-02-10 11:42:31 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-oe-core unspecified Other x86 VERIFIED NOTABUG Medium normal 1.6 M2 1 alexandru.c.georgescu tom.zanussi --- --- No (bug/feature does not impact docs) oldest_to_newest 39233 0 alexandru.c.georgescu 2013-12-05 10:31:12 +0000 poky: c51730aaa91066cfb51ad6ec2920fb4f9d9ea94c QEMU image used: http://autobuilder.yoctoproject.org/pub/releases/1.6_M1.rc1/machines/qemu/qemux86/core-image-sato-sdk-qemux86.tar.bz2 Errors appear when running "$ perf test" in qemux86: root@qemux86:~# perf test 1: vmlinux symtab matches kallsyms : Skip 2: detect open syscall event : Ok 3: detect open syscall event on all cpus : Ok 4: read samples using the mmap interface : Ok 5: parse events tests : Warning: function scsi_trace_parse_cdb not defined Warning: function scsi_trace_parse_cdb not defined Warning: function scsi_trace_parse_cdb not defined Warning: function scsi_trace_parse_cdb not defined Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: bad op token { Warning: Error: expected type 4 but read 0 Warning: function jiffies_to_msecs not defined Warning: function jiffies_to_msecs not defined Warning: unknown op '{' Warning: unknown op '{' Ok 6: x86 rdpmc test :Error: sys_perf_event_open() syscall returned with -1 (No such file or directory) FAILED! 7: Validate PERF_RECORD_* events & perf_sample fields : FAILED! 8: Test perf pmu format parsing : Ok 9: Test dso data interface : Ok 10: roundtrip evsel->name check : Ok 11: Check parsing of sched tracepoints fields : FAILED! 12: Generate and check syscalls:sys_enter_open event fields: Ok 13: struct perf_event_attr setup :sh: /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/x86_64-linux/usr/bin/python-native/python: No such file or directory FAILED! 14: Test matching and linking mutliple hists : Ok 15: Try 'use perf' in python, checking link problems : FAILED! 16: Test breakpoint overflow signal handler : FAILED! 17: Test breakpoint overflow sampling : FAILED! 18: Test number of exit event of a simple workload : Skip 19: Test software clock events have valid period values : Ok root@qemux86:~# 39247 1 dvhart 2013-12-05 15:47:47 +0000 Tom, can you have a look at this please? Do we expect this to work on all BSPs or is there a debug/tracing feature required? 39248 2 tom.zanussi 2013-12-05 15:52:20 +0000 A quick look at the output seems to show it trying to parse e.g. scsi events, which may not be there if scsi isn't enabled in the kernel. My first question is if this is a regression - I don't recall this test being run before - or is this a new QA test? 39250 3 alexandru.c.georgescu 2013-12-05 16:00:30 +0000 (In reply to comment #2) > A quick look at the output seems to show it trying to parse e.g. scsi > events, which may not be there if scsi isn't enabled in the kernel. > > My first question is if this is a regression - I don't recall this test > being run before - or is this a new QA test? Hi Tom, We don't usually test this, but I stumbled on it by testing eclipse-pluign. Eclipse has a tool that gives the developers the ability to use perf. So it was me just trying "perf test" in the Eclipse plugin and see what's the output. I cannot tell if it's a regression or not since. I also tested it on qemux86. On qemux86-64 gives slightly similar issues. I don't know for the other arches but I suspect similar output as well. 39482 4 tom.zanussi 2013-12-18 19:13:21 +0000 perf testing shouldn't be done using qemu, which doesn't properly emulate the PMU. From qemux86 dmesg: Performance Events: Broken PMU hardware detected, using software events only. 39483 5 tom.zanussi 2013-12-18 19:14:34 +0000 See previous entry - not expected to work on qemu. 40269 6 alexandru.c.georgescu 2014-02-10 11:42:31 +0000 verified as per Tom's comments.