[lttng-dev] [RFC PATCH 0/2] babeltrace legacy LTT 2.6 converter

[Matthew Khouzam]

Hi Jan,

I have a few questions about the patch:
Does it handle lost events?
I think we would need to bring in a state system for this
Is there a reason lttng2.0 is not working for you? kernel? install base?
other?
Do you want just a list of the events or analysis on the trace later on.

Can you post an example of a converted trace?
Thanks
Matthew


On 13-04-19 06:20 AM, Jan Glauber wrote:
> Hi list,
>
> I've written a converter that can read LTT's 2.6 trace format and convert it
> to a CTF trace format. This was discussed before on the list:
>
> http://lists.lttng.org/pipermail/lttng-dev/2011-June/015995.html
>
> and I roughly followed the guidance given by Mathieu there. Roughly because
> I did not create plugins but followed the approach of babeltrace-log.
>
> How it works:
> - babeltrace legacy converter gets a directory containing a LTT 2.6 trace
>   and a target directory where it will create the converted trace
> - it scans the metadata_N files and creates a CTF which fits the old trace data
> - it scans all trace files and creates CTF headers but copies the trace data
> - empty files which contain only headers are not copied
>
> Is there any interest in picking up this code for babeltrace (or is it just
> too obscure :) ?
>
> Best regards,
>
> Jan Glauber
> Harman Becker Automotive GmbH
> System Profiling & Optimizing Team
>
> Jan Glauber (2):
>   Resurrect LTT type parser
>   babeltrace legacy LTT 2.6 -> CTF 1.8 converter
>
>  converter/babeltrace-legacy.c        | 1184 ++++++++++++++++++++++++++++++++++
>  converter/ltt-type-parser.c          |  303 +++++++++
>  include/babeltrace/ltt-type-parser.h |   17 +
>  3 files changed, 1504 insertions(+)
>  create mode 100644 converter/babeltrace-legacy.c
>  create mode 100644 converter/ltt-type-parser.c
>  create mode 100644 include/babeltrace/ltt-type-parser.h
>