Re: EVL: hectic test fails when to many CPUs are available

Am 07.07.26 um 15:34 schrieb Philippe Gerum:
> Hannes Diethelm <[email protected]> writes:
> 
>> Hello
>>
>> This is the reason for the patch for evl-test. I guess a beginners mistake / edge case but
>> if you want to look into it:
>>
>> If I don't set evl.oobcpus in my VM or just use to many OOB CPUs, the hectic test crashes and
>> never exits. I have to use kill -9 to stop it.
>>
>> evl_attach(): Resource temporarily unavailable: This is probably not handled correctly.
>>
>> evl.oobcpus=0-15 -> Freeze
>> evl.oobcpus=1-15 -> Freeze
>> evl.oobcpus=2-15 -> Ok
>>
>> /usr/libexec/evl/tests/hectic -T 5
>>
>> rtus_ufps11-10 rtuo11-11 rtuo11-12 rtuo_ufpp11-13 rtuo_ufpp11-14
>> rtuo_ufps11-15 rtuo_ufps11-16 rtuo_ufpp_ufps11-17 rtuo_ufpp_ufps11-18
>> fpu_stress_ufps11-19 switcher_ufps12-0 rtk12-1 rtk12-2 rtup12-3
>> revl_attach(): Resource temporarily unavailable
>>
> 
> Mm, ok. This one is indeed an old and obscure issue which has never been
> cared of. Increasing CONFIG_EVL_COREMEM_SIZE and CONFIG_EVL_NR_THREADS
> in order to account for the massive amount of threads involved in large
> CPU configurations should fix it.
> 
> At any rate, the test should unwind and exit cleanly when that fails,
> so there is still this issue to solve at some point.
> 

The supplied patch should fix the issue with the forever running hectic
test. It looks like the main thread waited forever for the task_init semaphore.

Probably not a fully clean way of doing it but it exits now with a many error messages
in case there is not enough memory instead of running forever.