On 14.12.21 04:15, Hongzhan Chen wrote:
> For Xenomai-cobalt enabled system, cobalt_switch_context means that there
> is context switch in companion core(realtime core), which we may need
> to do special treatment and take correct action as main kernel sched_switch.
> We need to update cpu bar regarding cobalt_switch_context event to correct
> color as switching-in task.
It's tricker... I have trace with the following sequence here:
gdb-898 [000] 753.944137: cobalt_switch_context:
prev_name=ROOT/0 prev_pid=0 prev_prio=-1 prev_state=0x218008 ==>
next_name=pthelper next_pid=912 next_prio=3
gdb-898 [000] 753.944142: cobalt_timer_start:
timer=0xef7e8200([watchdog]) value=4000000000 interval=0 mode=0x0
pthelper-912 [000] 753.944172: cobalt_shadow_hardened:
state=0x240840 info=0x0
Your plugin correctly switches colors on cobalt_switch_context, but that
cobalt_timer_start is still running under the previous pid, causing a
color switch-back and than forth on cobalt_shadow_hardened. We need to
understand why and possibly fix that or rethink the visualization.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
