GSoC Project | Basic Support for Trace Compass

[Sebastian Huber]

On 31/07/2019 08:30, Ravindra Kumar Meena wrote:
>      > The bit field is documented in the manual. I would simplify this to:
>      >
>      > cctx->switch_out_int[ item->cpu ].prev_state = ( ( ( item->data
>      >> 24 )
>      > & 0x7 ) == 1 ) ? TASK_IDLE : TASK_RUNNING;
> 
>     Did you check how the Trace Compass behaviour changed with this?
> 
> Yes. I imported the trace on Trace Compass. The CPU 5 Threads and CPU 5 
> States lines are straight in the beginning because there is no change in 
> the cpu_id. At the end of the trace, there is a lot of change in cpu_id 
> due to which Trace Compass shows other CPU thread and state lines.
> 
> I have attached the screenshot of trace compass. Have a look.

Yes, this is similar to what I see. I don't think this is what we want. 
The 09.. are all idle threads. What I want is something similar to the 
LTTNG output, see attached screen shot.

It seems the prev_state is actually the state of the new thread. Doesn't 
really make sense to me. Could you please clarify this with the LTTNG 
mailing list?

-- 
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.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_20190802_102013.png
Type: image/png
Size: 227709 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190802/fb19d7c3/attachment-0002.png>