GSoC Project | Basic Support for Trace Compass

[Sebastian Huber]

On 25/07/2019 10:44, Ravindra Kumar Meena wrote:
> [19:16:31.180362596] (+0.000013856) Record_Item sched_switch: { cpu_id = 
> 5 }, { prev_comm = "0a01002b", prev_tid = 167837739, prev_prio = 0, 
> prev_state = 0, next_comm = "09010015", next_tid = 151060501, next_prio 
> = 0 }
> [19:16:31.180397048] (+0.000034452) Record_Item sched_switch: { cpu_id = 
> 5 }, { prev_comm = "09010015", prev_tid = 151060501, prev_prio = 0, 
> prev_state = 0, next_comm = "0a01002b", next_tid = 167837739, next_prio 
> = 0 }
> 
> Both prev_* and next_* values are different.

Ok, very good. This look all right. It is amazing how much information 
Trace Compass can display with only sched_switch events.

Please figure out how the state member values are defined. I think this 
is important to improve the diagrams.

It would be good to get task names for the IDs. Do you have an idea how 
we can do this?

-- 
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_20190725_110706.jpeg
Type: image/jpeg
Size: 181989 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190725/1f33de38/attachment-0002.jpeg>