On 19/07/2019 08:38, Ravindra Kumar Meena wrote:
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?
Please figure out what values are possible for the state field.
You need the RTEMS_RECORD_THREAD_SWITCH_IN and
RTEMS_RECORD_THREAD_SWITCH_OUT records to generate a sched_switch event.
For the comm fields just convert the record.data into a string. For the
tid fields use the record.data.
Set the priority fields to zero.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
