From: David Laight <David.Laight@ACULAB.COM>
To: 'Steven Rostedt' <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>
Subject: RE: ftrace trace_raw_pipe format
Date: Wed, 18 Dec 2019 17:28:13 +0000 [thread overview]
Message-ID: <3df0aa9c69ec4d2086b96eb032a1a0df@AcuMS.aculab.com> (raw)
In-Reply-To: <20191217173403.61f4e2d8@gandalf.local.home>
From: Steven Rostedt
> Sent: 17 December 2019 22:34
>
> > I'm trying to 'grok' the trace_raw_pipe data that ftrace generates.
> > I've some 3rd party code that post-processes it, but doesn't like wrapped traces
> > because (I think) the traces from different cpus start at different times.
> >
> > I can't seem to find any documentation at all...
...
> You may want to use libtraceevent (which will, hopefully, soon
> be in debian!). Attached is a simple program that reads the data using
> it and prints out the format.
The problem is that I don't want to print the trace, I want to fix
some trace files so that another program doesn't barf at them.
I guess I can try to reverse engineer the library code.
It would also be nice if there was a way that some standard program
(like cat) could read out the trace files without blocking at the end
when the trace is inactive.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-12-18 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 17:44 ftrace trace_raw_pipe format David Laight
2019-12-17 22:34 ` Steven Rostedt
2019-12-17 22:43 ` Steven Rostedt
2019-12-17 22:47 ` Steven Rostedt
2019-12-17 23:36 ` Steven Rostedt
2019-12-17 23:54 ` Steven Rostedt
2019-12-18 16:31 ` Sudip Mukherjee
2019-12-18 17:28 ` David Laight [this message]
2019-12-18 17:59 ` Steven Rostedt
2020-01-07 13:49 ` David Laight
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=3df0aa9c69ec4d2086b96eb032a1a0df@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudipm.mukherjee@gmail.com \
/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