Potential SIS or RTEMS/libbsd problem

Jiri Gaisler jiri at gaisler.se
Thu May 23 16:37:03 UTC 2019

On 5/23/19 1:47 PM, Sebastian Huber wrote:
> On 22/05/2019 22:34, Jiri Gaisler wrote:
>> Adding a pseudo-random delay of 0 - 15 clocks to each trap/interrupt
>> causes the test to pass on all cpu configurations with the default
>> time slice (50)..! I am not sure what this means - it could be a
>> hidden race condition, the algorithm might need some jitter to work
>> or it could still be a simulator issue.
> Adding a pseudo-random delay to interrupts is probably not enough.
> Sometimes the atomic instructions are carried out with interrupts
> disabled. Would it be possible to add a pseudo-random delay to each of
> the instruction cycles per core?

I think this is what I have done. The interrupt/trap latency for each
core get a random delay, which causes the instruction count to vary for
each core. The delay varies dynamically for each trap/core, and applies
to all traps not just interrupts (window underflow etc.).


More information about the devel mailing list