* Trouble parsing trace events
@ 2011-11-23 6:51 Arun Sharma
2011-11-23 7:03 ` Andrew Vagin
0 siblings, 1 reply; 3+ messages in thread
From: Arun Sharma @ 2011-11-23 6:51 UTC (permalink / raw)
To: linux-perf-users; +Cc: David Ahern, Andrew Vagin
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Trouble parsing trace events 2011-11-23 6:51 Trouble parsing trace events Arun Sharma @ 2011-11-23 7:03 ` Andrew Vagin 2011-11-23 7:14 ` Arun Sharma 0 siblings, 1 reply; 3+ messages in thread From: Andrew Vagin @ 2011-11-23 7:03 UTC (permalink / raw) To: Arun Sharma; +Cc: linux-perf-users, David Ahern Hello Arun, This bug was fixed already, but the commit isn't in Linus's tree yet. http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=49908a1b25d448d68fd26faca260e1850201575f On 11/23/2011 10:51 AM, Arun Sharma wrote: > > 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Trouble parsing trace events 2011-11-23 7:03 ` Andrew Vagin @ 2011-11-23 7:14 ` Arun Sharma 0 siblings, 0 replies; 3+ messages in thread From: Arun Sharma @ 2011-11-23 7:14 UTC (permalink / raw) To: avagin; +Cc: linux-perf-users, David Ahern On 11/22/11 11:03 PM, Andrew Vagin wrote: > Hello Arun, > > This bug was fixed already, but the commit isn't in Linus's tree yet. > http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=49908a1b25d448d68fd26faca260e1850201575f Thanks. I was confused about where various git trees live these days and was fetching from git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git which doesn't have the commit you're referring to. -Arun ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-11-23 7:14 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-11-23 6:51 Trouble parsing trace events Arun Sharma 2011-11-23 7:03 ` Andrew Vagin 2011-11-23 7:14 ` Arun Sharma
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).