Propagate trace format all the way to the consumer
authorJonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Thu, 18 Aug 2022 20:39:37 +0000 (16:39 -0400)
committerJonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Fri, 19 Aug 2022 15:54:32 +0000 (11:54 -0400)
commit8696b40b84aefe0800e9e5facb461ef4ad0fd370
treefe6a9edc6c2aa68d9cfe4f48cdfa5f32499aa5a1
parent8af3bd5768947013629cb38edbce0deed48c6c11
Propagate trace format all the way to the consumer

TODO: currently we end up propagating and exposing the trace format as a
vulgar integer on lttng-consumerd side. This is one of the frontier we
discussed IRL.

TODO: use the trace format serialize and pass a complete trace format
object on the pipe

Note that this is necessary to later decide if the consumerd strips the
ringbuffer header or not based on the ctf version. As discussed IRL, ust
could be modified to expose an API allowing us to set the ctf version thus
propagating the ctf version inside the ringbuffer header and perofming
introspection at the consumer level and split based on the value. This
was simply easier to do since we have all the data available at hand.

Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Change-Id: I4d12692fe2cab8ad9bf22db9b1d455ec397fa843
src/bin/lttng-sessiond/consumer.cpp
src/bin/lttng-sessiond/consumer.hpp
src/bin/lttng-sessiond/kernel-consumer.cpp
src/common/consumer/consumer-stream.cpp
src/common/consumer/consumer-stream.hpp
src/common/consumer/consumer.cpp
src/common/consumer/consumer.hpp
src/common/kernel-consumer/kernel-consumer.cpp
src/common/sessiond-comm/sessiond-comm.hpp
src/common/ust-consumer/ust-consumer.cpp
This page took 0.027387 seconds and 5 git commands to generate.