Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Jan Kiszka via Xenomai
On 14.04.22 17:41, Richard Weinberger wrote: > - Ursprüngliche Mail - >>> Did the nucleus CPU scheduler guarantee that giving another task >>> the same priority of the calling task will favour the caller? >>> Now the gifted task seems to win. >> >> Did you configure with

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Richard Weinberger via Xenomai
- Ursprüngliche Mail - >> Did the nucleus CPU scheduler guarantee that giving another task >> the same priority of the calling task will favour the caller? >> Now the gifted task seems to win. > > Did you configure with --enable-lazy-setsched? If not, set_prio should > send the caller to

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Jan Kiszka via Xenomai
On 14.04.22 17:13, Richard Weinberger wrote: > - Ursprüngliche Mail - >> Von: "Jan Kiszka" >>> task5 fails: >>> [9] at task-5.c:79 >>> [1] at task-5.c:23 >>> [10] at task-5.c:87 >>> [3] at task-5.c:40 >>> [11] at task-5.c:95 >>> [4] at task-5.c:45 >>> [5] at

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Richard Weinberger via Xenomai
- Ursprüngliche Mail - > Von: "Jan Kiszka" >> task5 fails: >> [9] at task-5.c:79 >> [1] at task-5.c:23 >> [10] at task-5.c:87 >> [3] at task-5.c:40 >> [11] at task-5.c:95 >> [4] at task-5.c:45 >> [5] at task-5.c:50 >> [6] at task-5.c:55 >>

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Richard Weinberger via Xenomai
- Ursprüngliche Mail - > Von: "Florian Bezdeka" >> ...same does marking both variables as volatile. > > I don't have much context here, but volatile sounds like a valid > solution (assuming that safety is written by a different thread) Both variables are written by the very same thread.

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Bezdeka, Florian via Xenomai
On Thu, 2022-04-14 at 14:58 +0200, Richard Weinberger via Xenomai wrote: > - Ursprüngliche Mail - > > Von: "Jan Kiszka" > > An: "richard" , "xenomai" > > Gesendet: Donnerstag, 14. April 2022 13:18:59 > > Betreff:

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Richard Weinberger via Xenomai
- Ursprüngliche Mail - > Von: "Jan Kiszka" > An: "richard" , "xenomai" > Gesendet: Donnerstag, 14. April 2022 13:18:59 > Betreff: Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests > On 13.04.22 23:58, Richard Weinberger via Xenomai w

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Richard Weinberger via Xenomai
- Ursprüngliche Mail - > Von: "Jan Kiszka" > Seems we need to fix those at least. Agreed. >> >> If Xenomai was configured with --enable-lores-clock, tests mq1, mutex1, >> pip1 and >> sem1 fail due to: >> undefined symbol: __clockobj_ticks_to_timeout > > Missing lib

Re: [PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-14 Thread Jan Kiszka via Xenomai
On 13.04.22 23:58, Richard Weinberger via Xenomai wrote: > This patch series is a first attempt to integrate the currently abandoned > alchemy, pSOS and VxWorks tests into Xenomai's test suite. > Since each test assumes running as own process a test driver is needed > which executes each tests

[PATCH v2 0/9] Revive alchemy, pSOS and VxWorks tests

2022-04-13 Thread Richard Weinberger via Xenomai
This patch series is a first attempt to integrate the currently abandoned alchemy, pSOS and VxWorks tests into Xenomai's test suite. Since each test assumes running as own process a test driver is needed which executes each tests separately. The driver makes use of the smokey framework. Test