On 25/07/2019 09:24, Ravindra Kumar Meena wrote:
>
https://github.com/rmeena840/rtems-tools/commit/f7838f156006064ffc53b1b1d3fb01f80ef15ae4
No, sorry, this is not what we need. Maybe you should delete this code
part and start from scratch.
We process record events and produce LTTNG events. Is this clear?
Your task is:
1. Gather the information from two record events
(RTEMS_RECORD_THREAD_SWITCH_OUT and RTEMS_RECORD_THREAD_SWITCH_IN) with
the same timestamp on the same CPU.
A CPU can have many records events. Since RTEMS_RECORD_THREAD_SWITCH_IN
is received after RTEMS_RECORD_THREAD_SWITCH_OUT we can just directly
write into corresponding CPU file after receiving
RTEMS_RECORD_THREAD_SWITCH_IN for the same timestamp.
Yes.
All the record handling must be done per CPU.
2. Once you gathered the information of two events that meet this
criteria, you produce exactly one LTTNG sched_switch event.
Okay. So this particular lttng sched_switch will have prev_* value
as RTEMS_RECORD_THREAD_SWITCH_OUT data and next_* value
as RTEMS_RECORD_THREAD_SWITCH_IN.
Yes.
--
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
