Re: RTEMS SMP Status Report v3

On 22/12/2016 01:19, Sebastian Huber wrote: The POSIX API provides no binary semaphores, so task/interrupt synchronization is a problem. So, for drivers there is still a need for some RTEMS-specific APIs. I like the idea of NP additions help us here. We already have pthread_getaffinity_np.

Re: POSIX compliance development

On Tue, Dec 20, 2016 at 2:53 PM, Gedare Bloom wrote: > Option #1 writing a script is better. We occasionally add > implementations for POSIX features as needed for various compliance > test requirements or application portability. > > POSIX compliance is desirable within the

[PATCH 8/8] Adding pipe support

--- testsuite/selectpollkqueue01/test_main.c | 183 ++- 1 file changed, 181 insertions(+), 2 deletions(-) mode change 100644 => 100755 testsuite/selectpollkqueue01/test_main.c diff --git a/testsuite/selectpollkqueue01/test_main.c

[PATCH 1/8] Adding pipe support

--- freebsd/sys/kern/sys_pipe.c | 1689 +++ 1 file changed, 1689 insertions(+) create mode 100644 freebsd/sys/kern/sys_pipe.c diff --git a/freebsd/sys/kern/sys_pipe.c b/freebsd/sys/kern/sys_pipe.c new file mode 100644 index 000..f1efd09 --- /dev/null

[PATCH 4/8] Adding pipe support

--- libbsd_waf.py | 1 + 1 file changed, 1 insertion(+) diff --git a/libbsd_waf.py b/libbsd_waf.py index 7ea6a36..c440015 100644 --- a/libbsd_waf.py +++ b/libbsd_waf.py @@ -836,6 +836,7 @@ def build(bld): 'freebsd/sys/kern/subr_uio.c',

[PATCH 7/8] Adding pipe support

--- rtemsbsd/sys/fs/devfs/devfs_devs.c | 29 + 1 file changed, 29 insertions(+) mode change 100644 => 100755 rtemsbsd/sys/fs/devfs/devfs_devs.c diff --git a/rtemsbsd/sys/fs/devfs/devfs_devs.c b/rtemsbsd/sys/fs/devfs/devfs_devs.c old mode 100644 new mode 100755 index

[PATCH 5/8] Adding pipe support

--- freebsd/sys/sys/pipe.h | 2 ++ 1 file changed, 2 insertions(+) mode change 100644 => 100755 freebsd/sys/sys/pipe.h diff --git a/freebsd/sys/sys/pipe.h b/freebsd/sys/sys/pipe.h old mode 100644 new mode 100755 index 20b1092..c59ecc7 --- a/freebsd/sys/sys/pipe.h +++ b/freebsd/sys/sys/pipe.h @@

[PATCH 3/8] Adding pipe support

--- libbsd.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/libbsd.py b/libbsd.py index 3685191..d7a0a5f 100755 --- a/libbsd.py +++ b/libbsd.py @@ -258,6 +258,7 @@ def base(mm): 'sys/sys/_null.h', 'sys/sys/osd.h', 'sys/sys/pcpu.h', +

[PATCH 2/8] Adding pipe support

--- freebsd/sys/sys/pipe.h | 142 + 1 file changed, 142 insertions(+) create mode 100644 freebsd/sys/sys/pipe.h diff --git a/freebsd/sys/sys/pipe.h b/freebsd/sys/sys/pipe.h new file mode 100644 index 000..20b1092 --- /dev/null +++

[PATCH 6/8] Adding pipe support

--- freebsd/sys/kern/sys_pipe.c | 271 1 file changed, 271 insertions(+) mode change 100644 => 100755 freebsd/sys/kern/sys_pipe.c diff --git a/freebsd/sys/kern/sys_pipe.c b/freebsd/sys/kern/sys_pipe.c old mode 100644 new mode 100755 index

Re: [PATCH] Enhancement of the RMS manager for the overrun handling.

Hello Gedare, I take the latest version of RTEMS eae4541d7b8001aa18c6fc2d62b32385b0310125 to integrate my patch this time. All you mentioned coding-convention issues are solved accordingly I think. I will hold the copyright by myself. rtems_rate_monotonic_postponed_num() this function is

[PATCH] Update RMS documentation for overrun handling

--- c-user/rate_monotonic_manager.rst | 30 +- 1 file changed, 17 insertions(+), 13 deletions(-) diff --git a/c-user/rate_monotonic_manager.rst b/c-user/rate_monotonic_manager.rst index 8ad74e5..9ba22a5 100644 --- a/c-user/rate_monotonic_manager.rst +++

[PATCH 1/3] Enhancement of the RMS manager for the overrun handling.

Three additional functions: RM_Postponed_num, RM_Renew_deadline, and RM_Release_postponedjob. Four refined functions: RM_Activate, RM_Block_while_expired, rtems_rate_monotonic_period, RM_Timeout. Rate_monotonic_Control contains one counter for counting the postponed jobs and one for recording

[PATCH 3/3] EDF scheduler overrun handling example

--- testsuites/sptests/Makefile.am | 2 +- testsuites/sptests/configure.ac | 1 + testsuites/sptests/spedfsched04/Makefile.am | 21 + testsuites/sptests/spedfsched04/init.c | 70 +++

[PATCH 2/3] RMS scheduler overrun handling example

--- testsuites/sptests/Makefile.am | 1 + testsuites/sptests/configure.ac| 1 + testsuites/sptests/sprmsched01/Makefile.am | 21 + testsuites/sptests/sprmsched01/init.c | 70 testsuites/sptests/sprmsched01/sprmsched01.doc |

Re: RTEMS SMP Status Report v3

Interesting. On our 40Mhz Coldfire CPU, one of our developers did note how the RTEMS semaphore calls were slow. So currently the self-contained objects are more efficient, but do not provide as many real-time features. Your changes to convert the POSIX objects to self-contained would help

Re: RTEMS SMP Status Report v3

On 21/12/16 15:02, Cudmore, Alan P. (GSFC-5820) wrote: I agree, it’s an excellent report. Thanks for the SMP implementation in RTEMS, it is very important to our future work. In the past I have used the classic RTEMS API. For SMP applications, is there a preferred API? Does the POSIX API

Re: RTEMS SMP Status Report v3

I agree, it’s an excellent report. Thanks for the SMP implementation in RTEMS, it is very important to our future work. In the past I have used the classic RTEMS API. For SMP applications, is there a preferred API? Does the POSIX API offer more control or features over the Classic API for