Re: Conflicting EVL Processing Loops

[Philippe Gerum <rpm@xenomai.org>]

Russell Johnson <russell.johnson@kratosdefense.com> writes:

> [[S/MIME Signed Part:Undecided]]
> Hello,
>
> We have two independent processing loops, each consisting of their own set
> of EVL threads and interrupts. Each loop completes its processing and then
> performs an evl_sleep_until to delay until the next processing deadline
> occurs. If we run either loop by itself, everything is fine, and our timing
> margins are met. However, if we try to run both simultaneously, the timing
> error is increased significantly, and the loops never meet their processing
> deadlines. If we compile the code for Linux (substituting all EVL primitives
> with Linux equivalents), then we are able to run both loops simultaneously
> without issue. Any clue what could be causing us troubles or where to start
> looking?
>

In absence of any code to review, the question is too broad to figure
out what might happen. Quick check though: make sure to disable all the
kernel debug options which may be turned on for your EVL kernel
(PROVE_LOCKING, DEBUG_LIST, KASAN and others). evl check may help with
this.

-- 
Philippe.