|Re: [tracecompass-dev] lttng-ust custom latency views?|
On the Trace Compass, as Jonathan mentioned, the XML analyses  might be a good starting point. The segments analyses in particular include min/max, latency and statistics analyses with some built-in views. If you decide to go this way, here's also a blog post by one Trace Compass user about his usage of the XML analyses .
But doing python analyses is a reasonable approach too. I'm not
too sure what the error may be though. Have you tried doing the
same not on an ARM board? Or with more recent version of
On 2018-07-11 09:37 AM, Martin Oberhuber wrote: