> > This looks very nice. > > The next step is to translate the record items into corresponding events > of LTTNG. We should start with the following event which I guess is used > by Trace Compass for the task switch view. I don't know it, we have to > try it out. We can also look at the analyses package from LTTNG instead > of Trace Compass: > > https://github.com/lttng/lttng-analyses > > event { > name = "sched_switch"; > id = 22; > stream_id = 0; > fields := struct { > integer { size = 8; align = 8; signed = 0; encoding = > UTF8; base = 10; > } _prev_comm[16]; > integer { size = 32; align = 8; signed = 1; encoding = > none; base = > 10; } _prev_tid; > integer { size = 32; align = 8; signed = 1; encoding = > none; base = > 10; } _prev_prio; > integer { size = 64; align = 8; signed = 1; encoding = > none; base = > 10; } _prev_state; > integer { size = 8; align = 8; signed = 0; encoding = > UTF8; base = 10; > } _next_comm[16]; > integer { size = 32; align = 8; signed = 1; encoding = > none; base = > 10; } _next_tid; > integer { size = 32; align = 8; signed = 1; encoding = > none; base = > 10; } _next_prio; > }; > }; > Okay. We need to have the values of event fields in client-side. What values should I pass there?
-- *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
