*Plan of the week:* Last week I added packet.header, packet.context, event.header, env object in the metadata. I will continue to work on adding event object in the metadata.
I have added the few parts of the sched_switch event. https://github.com/rmeena840/rtems-tools/commit/7b1488364b86df5ec956bd787dc8eeea01c28a8f https://github.com/rmeena840/rtems-tools/commit/cd969dfde62966c4f99c26973620852dafc0f47f Have a look I had a look at trace compass examples. The possible values of the state in sched_switch event is 0, 1 and 1026 but mostly it is 0 or1. There is no fixed pattern I found in the example. There is one problem here we need the next_comm and next_tid value before actually next record item is generated in client-side. Thanks -- *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
