Re: Xenomai and Linux SCHED_FIFO threads Question

On 30.07.21 18:02, Rajesh Venkataraman via Xenomai wrote: > Hello, >We are trying to move our embedded real time application from RTOS to > Linux. So we first ported our RTOS application to a RT-Linux. In RT-Linux > we have cpu isolation and run our main realtime interrupt as a pthread > with

Xenomai and Linux SCHED_FIFO threads Question

Hello, We are trying to move our embedded real time application from RTOS to Linux. So we first ported our RTOS application to a RT-Linux. In RT-Linux we have cpu isolation and run our main realtime interrupt as a pthread with highest priority on the isolated core. Rest of the application on

[PATCH v3 5/5] testsuite/smokey/y2038: Adding test cases for mutex_timedlock64()

This patch was based on the patch sent out by Song and reworked. Especially - switched from CLOCK_MONOTONIC to CLOCK_REALTIME According to POSIX this service is based on CLOCK_REALTIME - Fixed some mutex leaks / missing pthread_mutex_destroy() - Removed some magic numbers used for

[PATCH v3 2/5] cobalt/posix/mutex: Harmonize pthread_mutex_timedlock() and sem_timedwait()

According to the POSIX spec the value of the timeout parameter needs not to be validated if the mutex/semaphore could be taken immediately. While the implementation of the semaphore timedwait (sem_timedwait()) allowed an invalid timeout pthread_mutex_timedlock() was failing with -EFAULT in case

[PATCH v3 1/5] smokey: posix_mutex: Fix mutex/smokey_barrier leak

The mutex of the smokey_barrier used inside protect_handover() was never destroyed. This had side effects when trying to extend the test suite with an additional function that had a mutex located on the same address than the never cleaned up smokey_barrier lock. Signed-off-by: Florian Bezdeka

[PATCH v3 3/5] y2038: cobalt/posix/mutex: Adding mutex_timedlock64

From: Song Chen Add a syscall specific for mutex_timedlock with 64bit time_t. Signed-off-by: Song Chen [Florian: Rearranged code, coding style fixes, tracing] Signed-off-by: Florian Bezdeka --- include/cobalt/uapi/syscall.h | 1 + kernel/cobalt/posix/mutex.c| 23

[PATCH v3 4/5] y2038: lib/cobalt/mutex: dispatch mutex_timedlock

From: Song Chen In case the libc in use reports a 64 bit time_t dispacht mutex_timedlock to the kernel entry point that accepts it. Signed-off-by: Song Chen Signed-off-by: Florian Bezdeka --- lib/cobalt/mutex.c | 4 1 file changed, 4 insertions(+) diff --git a/lib/cobalt/mutex.c

[PATCH v3 0/5] y2038: Add mutex_timedlock64() support

Hi! This series is based on the series posted by Song some time ago. The testing part has been heavily reworked. Details are mentioned in the description of the last patch. @Jan: Patch 1 and 2 are re-sends. They are not directly related to the y2038 stuff but the testsuite might fail if they

[PATCH v2 4/5] y2038: lib/cobalt/mutex: dispatch mutex_timedlock

From: Song Chen In case the libc in use reports a 64 bit time_t dispacht mutex_timedlock to the kernel entry point that accepts it. Signed-off-by: Song Chen Signed-off-by: Florian Bezdeka --- lib/cobalt/mutex.c | 4 1 file changed, 4 insertions(+) diff --git a/lib/cobalt/mutex.c

[PATCH v2 5/5] testsuite/smokey/y2038: Adding test cases for mutex_timedlock64()

This patch was based on the patch sent out by Song and reworked. Especially - switched from CLOCK_MONOTONIC to CLOCK_REALTIME According to POSIX this service is based on CLOCK_REALTIME - Fixed some mutex leaks / missing pthread_mutex_destroy() - Removed some magic numbers used for

[PATCH v2 2/5] cobalt/posix/mutex: Harmonize pthread_mutex_timedlock() and sem_timedwait()

According to the POSIX spec the value of the timeout parameter needs not to be validated if the mutex/semaphore could be taken immediately. While the implementation of the semaphore timedwait (sem_timedwait()) allowed an invalid timeout pthread_mutex_timedlock() was failing with -EFAULT in case

[PATCH v2 3/5] y2038: cobalt/posix/mutex: Adding mutex_timedlock64

From: Song Chen Add a syscall specific for mutex_timedlock with 64bit time_t. Signed-off-by: Song Chen [Florian: Rearranged code, coding style fixes] Signed-off-by: Florian Bezdeka --- include/cobalt/uapi/syscall.h | 1 + kernel/cobalt/posix/mutex.c | 23 ++-

[PATCH v2 1/5] smokey: posix_mutex: Fix mutex/smokey_barrier leak

The mutex of the smokey_barrier used inside protect_handover() was never destroyed. This had side effects when trying to extend the test suite with an additional function that had a mutex located on the same address than the never cleaned up smokey_barrier lock. Signed-off-by: Florian Bezdeka

[PATCH v2 0/5] y2038: Add mutex_timedlock64() support

Hi! This series is based on the series posted by Song some time ago. The testing part has been heavily reworked. Details are mentioned in the description of the last patch. @Jan: Patch 1 and 2 are re-sends. They are not directly related to the y2038 stuff but the testsuite might fail if they

Re: xenomai supported_cpus

thank you Jan, I will look into it and hopefully create a documentation soon! yours sincerely, John On Thu, Jul 29, 2021 at 11:01 AM Jan Kiszka wrote: > On 29.07.21 10:51, John Ho via Xenomai wrote: > > Hi all, I wish to ask about core isolation, and how to define the grub > > command line

Re: [PATCH] cobalt/posix/mutex: Harmonize pthread_mutex_timedlock() and sem_timedwait()

On 30.07.21 09:14, Bezdeka, Florian (T RDA IOT SES-DE) wrote: > On Thu, 2021-07-29 at 19:29 +0200, Jan Kiszka wrote: >> On 29.07.21 18:22, Bezdeka, Florian (T RDA IOT SES-DE) wrote: >>> On Thu, 2021-07-29 at 17:45 +0200, Jan Kiszka wrote: On 29.07.21 17:06, Philippe Gerum wrote: > >

Re: [PATCH] cobalt/posix/mutex: Harmonize pthread_mutex_timedlock() and sem_timedwait()

On Thu, 2021-07-29 at 19:29 +0200, Jan Kiszka wrote: > On 29.07.21 18:22, Bezdeka, Florian (T RDA IOT SES-DE) wrote: > > On Thu, 2021-07-29 at 17:45 +0200, Jan Kiszka wrote: > > > On 29.07.21 17:06, Philippe Gerum wrote: > > > > > > > > Florian Bezdeka writes: > > > > > > > > > According to the