summaryrefslogtreecommitdiffstats
path: root/cpukit/include/rtems/score/mrspimpl.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* rtems: Allow initially locked MrsP semaphoresSebastian Huber2021-03-161-6/+22
| | | | | | Rejecting initially locked MrsP semaphores was due to a limitiation of the early limitiation of the MrsP protocol. This limitation no longer exists.
* score: Simplify _MRSP_Wait_for_ownership()Sebastian Huber2021-02-011-7/+6
| | | | | | | Do not shadow the queue_context parameter with a local variable. Reuse the queue context to reduce the required stack space. This fix relates to a Coverity issue (PW.PARAMETER_HIDDEN).
* mrsp: Change error status for a nested seizeSebastian Huber2021-01-211-11/+19
| | | | | | | | Return STATUS_DEADLOCK (RTEMS_INCORRECT_STATE) to indicate a nested seize since this is a kind of deadlock. This status code is also used for other deadlocks. Update #4217.
* score: Canonicalize Doxygen @file commentsSebastian Huber2020-12-021-1/+2
| | | | | | Use common phrases for the file brief descriptions. Update #3706.
* rtems: Simplify semaphore configurationSebastian Huber2019-12-111-10/+1
| | | | | | | | | | | | | | | The MrsP semaphore implementation predates the addition of self-contained synchronization objects. At this time, the potential memory reduction was justified considering the more complex configuration and additional use of the workspace. With the availability of self-contained synchronization options, e.g. POSIX mutexes, this is no longer justified. Memory constrained applications should use the self-contained synchronization objects. Remove the CONFIGURE_MAXIMUM_MRSP_SEMAPHORES configuration option. This has only an impact on applications which use SMP and a large number of scheduler instances. Update #3833.
* doxygen: score: adjust doc in mrspimpl.h to doxygen guidelinesAndreas Dachsberger2019-05-131-0/+154
| | | | Update #3706.
* doxygen: Rename Score* groups in RTEMSScore*Sebastian Huber2019-04-041-1/+1
| | | | Update #3706
* Remove make preinstallChris Johns2018-01-251-0/+384
A speciality of the RTEMS build system was the make preinstall step. It copied header files from arbitrary locations into the build tree. The header files were included via the -Bsome/build/tree/path GCC command line option. This has at least seven problems: * The make preinstall step itself needs time and disk space. * Errors in header files show up in the build tree copy. This makes it hard for editors to open the right file to fix the error. * There is no clear relationship between source and build tree header files. This makes an audit of the build process difficult. * The visibility of all header files in the build tree makes it difficult to enforce API barriers. For example it is discouraged to use BSP-specifics in the cpukit. * An introduction of a new build system is difficult. * Include paths specified by the -B option are system headers. This may suppress warnings. * The parallel build had sporadic failures on some hosts. This patch removes the make preinstall step. All installed header files are moved to dedicated include directories in the source tree. Let @RTEMS_CPU@ be the target architecture, e.g. arm, powerpc, sparc, etc. Let @RTEMS_BSP_FAMILIY@ be a BSP family base directory, e.g. erc32, imx, qoriq, etc. The new cpukit include directories are: * cpukit/include * cpukit/score/cpu/@RTEMS_CPU@/include * cpukit/libnetworking The new BSP include directories are: * bsps/include * bsps/@RTEMS_CPU@/include * bsps/@RTEMS_CPU@/@RTEMS_BSP_FAMILIY@/include There are build tree include directories for generated files. The include directory order favours the most general header file, e.g. it is not possible to override general header files via the include path order. The "bootstrap -p" option was removed. The new "bootstrap -H" option should be used to regenerate the "headers.am" files. Update #3254.