[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADVatmN-5W5J=dn1y9fuuV32bE-NmUpEd8983KLO3Jsf0d5G4g@mail.gmail.com>
Date: Wed, 18 Dec 2019 16:31:41 +0000
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: David Laight <David.Laight@...lab.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: ftrace trace_raw_pipe format
On Tue, Dec 17, 2019 at 10:34 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Tue, 17 Dec 2019 17:44:40 +0000
> David Laight <David.Laight@...LAB.COM> wrote:
>
> > 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.
> >
<snip>
>
> 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.
merge request has been opened in debian, waiting for the debian
kernel-team to review and merge it,
--
Regards
Sudip
Powered by blists - more mailing lists