[lttng-dev] What is _prev_state in sched_switch?

Ravindra Kumar Meena rmeena840 at gmail.com
Wed Jul 24 02:44:40 EDT 2019


Hi,

I had a looked at TraceCompass example. I came across sched_swithc event in
present in the metadata.

event {
name = "sched_switch";
id = 27;
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;
};
};

All event.fields variables are clear to me but what does _prev_state do
here? I had a looked at its babeltrace output but found no pattern in
_prev_state value.

Please attend this email ASAP.

Thanks

-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20190724/67d29fa9/attachment.html>


More information about the lttng-dev mailing list