From: Christoph Hellwig <hch@lst.de>
To: fweisbec@gmail.com, mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: perf trace errors
Date: Sun, 11 Oct 2009 04:54:41 +0200 [thread overview]
Message-ID: <20091011025441.GA18152@lst.de> (raw)
I get some rather interesting errors using perf trace with the block
tracepoints on current mainline, e.g.:
perf record -f -e 'block:block_bio_queue:record' -R -F 1 -a -s
<do some disk I/O end then ctrl+c>
^C[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.237 MB perf.data (~10362 samples) ]
brick:/home/hch# perf trace
Fatal: unknown op '-'
xfssyncd-4232 [000] 87.798249255: block_bio_queue: 253,
There are lots of occurances of that exactly same warning in
builtin-trace.c, and the code sourrouning them is sufficiently enough
convoluted that I'm not able to track it down.
next reply other threads:[~2009-10-11 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 2:54 Christoph Hellwig [this message]
2009-10-11 12:19 ` perf trace errors Frederic Weisbecker
2009-10-11 12:40 ` Christoph Hellwig
2009-10-11 20:23 ` Frederic Weisbecker
2009-10-16 8:32 ` Ingo Molnar
2009-10-25 7:17 ` Christoph Hellwig
2009-10-25 23:43 ` Frederic Weisbecker
2009-10-29 21:24 ` Steven Rostedt
2009-11-02 1:24 ` Frederic Weisbecker
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=20091011025441.GA18152@lst.de \
--to=hch@lst.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox