> > This is not a proper argument. You should use the packet context to > indicate the CPU of the events. >
I have added the ctf_header in rtems_main.c https://github.com/rmeena840/rtems-tools/commit/5a1c7b6e3c0c5246a8afc538f9f01576a5ac7983 Tested on AWS. No warning from my end. Now, each binary stream file has format: <stream_id=0> <cpu_id> <ns> <event> <data> <ns> <event> <data> ........ I have stream_id = 0 because in metadata there is one stream with id=0 so it has to be there. Both stream_id and cpu_id is playing the role of header. Here the modified metadata: https://github.com/rmeena840/rtems-tools/commit/afc73eb33c4366d81d63330f35e03af5df1410f5 The metadata has the same format as described above. Babeltrace is able to read values. Here is the output: 0 RTEMS_RECORDING_EVENT: { cpu_id = 4 }, { ns = 954631069457, events = ( "RTEMS_RECORD_THREAD_STACK_CURRENT" : container = 209 ), data = 134621454958589 } 0 RTEMS_RECORDING_EVENT: { cpu_id = 18 }, { ns = 955492534605, events = ( "RTEMS_RECORD_THREAD_SWITCH_OUT" : container = 216 ), data = 720857707413798909 } 0 RTEMS_RECORDING_EVENT: { cpu_id = 19 }, { ns = 955499514125, events = ( "RTEMS_RECORD_THREAD_SWITCH_IN" : container = 215 ), data = 648799898627506173 } As you can see. It now includes cpu_id also. -- *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
