All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <asharma@fb.com>
To: linux-perf-users@vger.kernel.org
Cc: David Ahern <dsahern@gmail.com>, Andrew Vagin <avagin@gmail.com>
Subject: Trouble parsing trace events
Date: Tue, 22 Nov 2011 22:51:23 -0800	[thread overview]
Message-ID: <4ECC97EB.1040008@fb.com> (raw)


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

             reply	other threads:[~2011-11-23  6:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23  6:51 Arun Sharma [this message]
2011-11-23  7:03 ` Trouble parsing trace events Andrew Vagin
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=4ECC97EB.1040008@fb.com \
    --to=asharma@fb.com \
    --cc=avagin@gmail.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.