From: Andrew Vagin <avagin@gmail.com>
To: Arun Sharma <asharma@fb.com>
Cc: linux-perf-users@vger.kernel.org, David Ahern <dsahern@gmail.com>
Subject: Re: Trouble parsing trace events
Date: Wed, 23 Nov 2011 11:03:52 +0400 [thread overview]
Message-ID: <4ECC9AD8.3010801@gmail.com> (raw)
In-Reply-To: <4ECC97EB.1040008@fb.com>
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
next prev parent reply other threads:[~2011-11-23 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 6:51 Trouble parsing trace events Arun Sharma
2011-11-23 7:03 ` Andrew Vagin [this message]
2011-11-23 7:14 ` Arun Sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECC9AD8.3010801@gmail.com \
--to=avagin@gmail.com \
--cc=asharma@fb.com \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.