I'm using a 3.2-rc1 based kernel and perf userspace built from
tip/auto-latest (commit id e471db8) + Andrew Vagin's sleep profiling
patches.
# perf record -agT -e sched:sched_switch -F 100 -- sleep 3
[ perf record: Woken up 9 times to write data ]
[ perf record: Captured and wrote 4.044 MB perf.data (~176664 samples) ]
# perf script
Warning: Error: expected type 5 but read 4
Warning: Error: expected type 4 but read 0
Fatal: bad op token {
Is there a known incompatibility between kernel and userspace that could
explain this?
I don't see this problem with other trace points (eg: kmem:kmalloc).
-Arun
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
