On 12/07/2019 09:27, Ravindra Kumar Meena wrote:
I have added the stream_instance_id and set it to 0. I have raised a query on lltng mailing list for the same.https://github.com/rmeena840/rtems-tools/commit/44552ac5bb9eca70008f1784aa15419d3cf98b8b https://github.com/rmeena840/rtems-tools/commit/4525ca1770ed9233e59e1e5c185d13003a2913b7 Now, I am working on stream.packet.context. struct packet_context { uint64_clock_monotonic_t timestamp_begin; uint64_clock_monotonic_t timestamp_end; uint64_t content_size; uint64_t packet_size; uint64_t packet_seq_num; unsigned long events_discarded; uint32_t cpu_id; };timestamp values are needed in the client-side program. Where to obtain in client side?
When you process the first record, you get the timestamp_begin. When you process the last record, you get the timestamp_end.
-- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : [email protected] PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ devel mailing list [email protected] http://lists.rtems.org/mailman/listinfo/devel
