Track down in-band switches

Track down in-band switches

[Russell Johnson]

Hello,

 

I am currently working on porting my realtime threads in my app to EVL. I am
using "evl ps -l" to track whether or not there are any in-band switches on
my EVL threads. Is there any recommended tool or method for tracking down
what specifically is causing the in-band switches on an EVL thread? 

 

 

Thanks,

____________

Russell Johnson

Software Development Engineer, Kratos Space

Kratos Defense & Security Solutions, Inc.

12515 Academy Ridge View
Colorado Springs, Colorado 80921
Main:  719.472.3323x1192

Direct: 719.884.6392

 <mailto:russell.johnson@kratosdefense.com>
russell.johnson@kratosdefense.com
 <http://www.kratosdefense.com/> www.kratosdefense.com



 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2582 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20220608/65177c62/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6759 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20220608/65177c62/attachment.bin>

Re: Track down in-band switches

[Philippe Gerum]

Russell Johnson via Xenomai <xenomai@xenomai.org> writes:

> Hello,
>
>  
>
> I am currently working on porting my realtime threads in my app to EVL. I am
> using "evl ps -l" to track whether or not there are any in-band switches on
> my EVL threads. Is there any recommended tool or method for tracking down
> what specifically is causing the in-band switches on an EVL thread? 
>

There are two additional options provided by the health monitoring
interface [1], both enabled with [2]:

- using the legacy signal-based method (T_HMSIG), which sends SIGDEBUG
  (a Xenomai alias to SIGXCPU) to the thread which switches in-band,
  with the cause for switch available from the siginfo data.

- using the 'observable' interface of any EVL thread (T_HMOBS) to
  receive message-based notifications instead of signals. In this case,
  a thread can observe other threads, i.e. receive those
  notifications. [4] is a simple test which illustrates how to use this
  interface.

[1] https://evlproject.org/core/user-api/thread/#health-monitoring
[2] https://evlproject.org/core/user-api/thread/#evl_set_thread_mode
[3] https://evlproject.org/core/user-api/observable/#observable-thread
[4] https://source.denx.de/Xenomai/xenomai4/libevl/-/blob/master/tests/observable-hm.c

-- 
Philippe.