Hi Steve, On 3/12/19 4:35 PM, Steven Rostedt wrote: > On Fri, 8 Mar 2019 15:47:14 +0000 > Tzvetomir Stoyanov <tstoyanov@xxxxxxxxxx> wrote: > >> Steven could describe it in more details, but we work on common >> tracing platform - set of libraries, which will expose the tracing >> functionality, currently available for trace-cmd and kernelshark only, >> to any application. > > [ Just came back from SCaLE 17x conference ] > > Note, the libtraceevent is currently just a way to parse the data read > by the Linux kernel trace events. The format files exist in the tracefs > file system under events/<system>/<event>/format (e.g. > events/sched/sched_switch/format). > > The library is used by trace-cmd, perf, powertop and mce utils. > Currently, each has their own copy. We are working on making this into > a shared library where the code no longer needs to be duplicated. > There's also going to be an effort to create libftrace, that will take > the functionality of trace-cmd and move it into a library, such that > any tool can start ftrace tracing, and record data. But that's not going > to happen until after we finish getting libtraceevent out. > > -- Steve > thank you for this background information, this solves my confusion at the moment. I currently have my own code that parses the data, based on the event/format, so I will not replace it immediately, I think that the really valuable replacement would be the libftrace follow up project. Ciao, CLaudio
|