Actions
Bug #1129
closedctf writer: the timestamp value's monotonicity is validated globally, not by stream
Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/03/2017
Due date:
% Done:
0%
Estimated time:
Description
I'm using babeltrace python bindings to write a CTF trace. My event is taken in an ebpf program where the timestamp is set, then sent to userspace via a perf buffer and then processed (written to ctf).
My events are monotonic in a stream (cpu). But it may happen that events from another stream with later timestamps are written before my current event, so they are not globally monotonic.
In the CTF writer (clock.c, method bt_ctf_clock_set_time), the timestamps are validated for monotonicity globally, so that my event raises an error and is not written.
Actions