[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3df0aa9c69ec4d2086b96eb032a1a0df@AcuMS.aculab.com>
Date: Wed, 18 Dec 2019 17:28:13 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Steven Rostedt' <rostedt@...dmis.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Sudip Mukherjee" <sudipm.mukherjee@...il.com>
Subject: RE: ftrace trace_raw_pipe format
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)
Powered by blists - more mailing lists