>
>-----Original Message-----
>From: Chen, Hongzhan
>Sent: Tuesday, December 7, 2021 11:11 AM
>To: xenomai@xenomai.org<mailto:xenomai@xenomai.org>; Jan Kiszka 
>jan.kis...@siemens.com<mailto:jan.kis...@siemens.com>
>Subject: questions about comments on 
>https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33
>
>Hi Jan
>
>I have some questions about comments on  
>https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/33 and need your help 
>to comment more.
>
>1. I do not quite understand the requirement "visualize task switches 
>correctly in Kernelshark (color in CPU bar is not updating on 
>cobalt_switch_context)".
>
>When I click the cobalt_switch_context event listed in the event table on the 
>second half in the kernelshark, actually color in cpu bar is updating to
>green because there is long green vertical  line to mark focused event like 
>attached picture.  In addition , In spite of focused thing,  colors mainly
>change depending on what task is running for cpu plots in kernelshark. when 
>cobalt_switch_context is traced, it still be in the prev context and its
>color is same with task prev in kernelshark. Do we want to update color of  
>cobalt_switch_context  to specific color different from all tasks even if 
>there is no
>focused thing?  What result do we need to achieve when there is 
>cobalt_switch_context, Could you be more specific?

After I understand what does means about sched_switch in kernelshark, I guess 
that we need to use cobalt_switch_context as dividing line for RT/non-RT tasks 
similar with sched_switch after we use xenomai.

Regards

Hongzhan Chen

>
>2. Regarding  the requirement " visualize RT/Non-RT (out-of-band/in-band) 
>state in CPU bar)",
>    2.1. Do we need to differentiate state  running a Linux task out-of-band 
> and running whatever code from the out-of-band execution stage as described in
>             " What you really need to know at this point" of  
> https://evlproject.org/dovetail/altsched/?
>    2.2 What state do we want to show  in CPU bar? Different color covering 
> the size of  RT/Non-RT state other than all tasks and CPUs?  If so, we may 
> ask for a plugin
>          in kernelshark , which would raise similar question as you mentioned 
> in comments.
>
>For the other two aspects, I still need more time to do research.
>
>
>Regards
>
>Hongzhan Chen

Reply via email to