On Tue, Aug 17, 2021 at 6:44 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > On Thu, 29 Jul 2021 08:09:03 +0300 > "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@xxxxxxxxx> wrote: > > > Trace file version 7 format is based on sections. To fit the latency > > trace data in this structure, a new section and option for it is > > defined: > > BUFFER_LAT > > It is similar to the BUFFER section which holds the flyrecord data, but > > has a latency specific design. The BUFFER_LAT section has: > > Actually, let's call it BUFFER_TEXT. > > Although we do it for "latency" format, which I'm thinking we should > call it something different for v7, the real difference is that it's > text and not binary. Perhaps we can save other formats as "text". > > In fact, I think v7 should allow for a mixture of TEXT and BINARY > buffers. It does, there is no limitation to do a flyrecord in one buffer and latency tracing in another. Although I cannot imagine a use case for that. > > -- Steve > > > - section header, as all other sections > > - compression of the trace data, optional > > - corresponding trace option, pointing to the section > > > > Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@xxxxxxxxx> -- Tzvetomir (Ceco) Stoyanov VMware Open Source Technology Center
|