From: Johannes Berg <johannes@sipsolutions.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: binary ftrace buffer format
Date: Tue, 14 Jul 2009 19:22:47 +0200 [thread overview]
Message-ID: <1247592167.7178.25.camel@johannes.local> (raw)
In-Reply-To: <1247520189.4071.4.camel@johannes.local>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
So, I've gotten this far, manually:
This was on a powerpc 64-bit (big endian) machine, the contents of
per_cpu/trace_pipe_raw:
00000000 00 00 02 24 15 cd b4 a0 00 00 00 00 00 00 0f f0 page header: time 2354.007880864, 4080 bytes
00000010 00 00 00 00 item header: type_len == 0, time offset = 0
00 00 00 94 item length: 148 bytes
00 82 event ID 130
11 02 00 00 00 00
00000020 00 00 00 00 00 00 00 00 c0 00 00 01 03 ca 1a 00
00000030 00 1a 70 00 00 00 01 00 00 80 39 e4 01 00 00 00
00000040 00 00 00 00 00 00 01 09 01 00 7c 10 80 00 ec 0f
00000050 80 00 00 00 00 00 01 00 00 00 ff ff ff ff 1a ff
00000060 ff ff 02 ff ff ff 20 34 00 00 e2 34 00 00 c4 ca
00000070 ff ff 94 c9 ff ff 66 f3 ff ff e6 f2 ff ff 00 00
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000090 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ff
000000a0 ff ff 00 00
00 00 00 00 item header: type_len == 0, time offset == 0
88 78 3d 40 item length???
00 82 event ID 130
11 02
at which point it stops making sense. What's with that item length? Can
anyone help?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-14 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:23 Johannes Berg
2009-07-14 17:22 ` Johannes Berg [this message]
2009-07-21 1:51 ` Steven Rostedt
2009-07-21 10:46 ` Johannes Berg
2009-07-22 11:36 ` Johannes Berg
2009-07-22 15:17 ` Steven Rostedt
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=1247592167.7178.25.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®