babeltrace python binding and multiple streams with out of order samples
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi Carlo,
Events do indeed need to be passed in order. You
can use a heap to sort the streams as they are read. This is the strategy used
by babeltrace to multiplex streams and present them chronologically.
Otherwise, if the streams contain the same event descriptions, you could convert
the per-CPU event sets independently and combine the stream files with a single metadata file to obtain a "complete" trace.
Regards,
Jérémie
Quoted 44 lines · Carlo Caione
Hi,
I'm using the babeltrace python bindings (v1.5.x) to convert some raw data I have into a CTF file.This raw data is organized in fixed data chunks composed by serializing the events for each CPU:
[cpu0, cpu0, cpu0, ..., cpu1, cpu1, cpu1, ..., cpu2,... ]
Each event for each CPU has a timestamp that is monotonic within each CPU set.
I wanted to create one stream per CPU and since the events are the same for each CPU, I was using a single
stream_classlinked to a stream object for each CPU. Something in the structure similar to [0] with:
stream_cpu0=writer.create_stream(stream_class)stream_cpu1=writer.create_stream(stream_class)stream_cpu2=writer.create_stream(stream_class)
...The problem is that being the clock one for the
stream_classwhen feeding the events to the library I get a:ValueError: Invalid time value
When the first event on cpu1 is parsed, because the timestamp is in the past with respect to the timestamp of the latest event of the cpu0.
I can sort the events before feeding them to babeltrace but this seems sub-optimal to me. My question is: am I using the library correctly or there is any way to achieve this?
Thank you,
[0] https://lists.lttng.org/pipermail/lttng-dev/2015-November/025231.html
--
Carlo Caione
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Signature · 3 lines
Jérémie Galarneau EfficiOS Inc. http://www.efficios.com
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev