On 14.12.21 08:46, Chen, Hongzhan wrote: > >>>>> >>>>> BTW, is that blue hollow box exclusive for our plugin? Or can this be >>>>> customized? Is it explained somewhere in Kernelshark what hollow boxes >>>>> mean? >>>>> >>>> >>>> Some visualization issue: >>>> >>>> pthelper-912 [000] 753.948271: cobalt_schedule: >>>> status=0x10000000 >>>> pthelper-912 [000] 753.948275: cobalt_switch_context: >>>> prev_name=pthelper prev_pid=912 prev_prio=3 prev_state=0xa40042 ==> >>>> next_name=hi-thread next_pid=913 next_prio=2 >>>> hi-thread-913 [000] 753.948285: cobalt_shadow_hardened: >>>> state=0x240040 info=0x0 >>>> hi-thread-913 [000] 753.948423: cobalt_thread_fault: >>>> ip=0xb6e34e20 type=0x8 >>>> hi-thread-913 [000] 753.948737: cobalt_shadow_gorelax: >>>> reason=syscall >>>> >>>> In this case, the task plot of hi-thread-919 does no show the blue box >>>> between hardened and fault. >>> >>> Could you zoom out (click "-" in the top left button) to check if blue box >>> would be reshowing? >>> Could you paste more trailing log in your log to check if there another >>> cobalt_switch_context. Current logic is create hollow box between two >>> cobalt_switch_context. If there is only cobalt switch_context event >>> matching, it would not create hollow box correctly. >>> >> >> Yeah, the problem is indeed that the bar is only drawn if beg AND end >> points are visible - that is sure not useful. Does the drawing concept >> of kernelshark imposes this limitation? > > This should be common issue in kernelshark. I also observed same > issue on hollow red box for preempt latency implementation. >
Ok, another topic to discuss with their community :) Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
