> > Yes, the values are there, but babeltrace cannot deduce the clock > source. In the LTTNG it displays it like this: > > [17:50:44.093076317] (+0.000002071) > Okay. The timestamp_begin and timestamp_end member in packet.context are for the whole recording process.
The timestamp_begin means first record item recorded in the whole process per CPU. The timestamp_end means the last record item recorded in the whole process per CPU. So I moved the timestamp value of individual record item in event.header https://github.com/rmeena840/rtems-tools/commit/0542b83c5f28ad2d005e8c0d86c0f4a13d43fee9 Now, babeltrace is able to print timestamp value now. It looks like this: babeltrace . | head [19:16:31.180116542] (+0.000000000) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_STACK_CURRENT" : container = 209 ), data = 5856 } [19:16:31.180116542] (+0.000000000) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_SWITCH_IN" : container = 215 ), data = 151060500 } [19:16:31.180154588] (+0.000038046) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_SWITCH_OUT" : container = 216 ), data = 151060500 } [19:16:31.180154588] (+0.000000000) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_STACK_CURRENT" : container = 209 ), data = 7392 } [19:16:31.180154588] (+0.000000000) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_SWITCH_IN" : container = 215 ), data = 167837739 } [19:16:31.180174232] (+0.000019644) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_SWITCH_OUT" : container = 216 ), data = 167837739 } [19:16:31.180174232] (+0.000000000) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 17 }, { events = ( "RTEMS_RECORD_THREAD_STACK_CURRENT" : container = 209 ), data = 5856 } -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) <https://www.iitism.ac.in/>, Dhanbad
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
