summaryrefslogtreecommitdiffstats
path: root/cpukit (follow)
Commit message (Collapse)AuthorAgeFilesLines
* score: Lazy key value pair allocationSebastian Huber2014-04-071-9/+13
|
* score: Delete _Thread_Ticks_per_timesliceSebastian Huber2014-04-078-15/+18
| | | | Use the Configuration instead.
* score: Delete _Thread_Maximum_extensionsSebastian Huber2014-04-073-18/+6
| | | | Use the Configuration instead.
* score: Fix POSIX threads size estimateSebastian Huber2014-04-071-12/+12
| | | | | The POSIX threads are separate objects. Account for the object administration overhead.
* score: Fix workspace size estimateSebastian Huber2014-04-071-7/+11
|
* score: Clarify CPU port alignment requirementsSebastian Huber2014-04-072-9/+42
|
* Disable per task variables when SMP is enabledJoel Sherrill2014-04-0411-30/+80
| | | | | | Per task variables are inherently unsafe in SMP systems. This patch disables them from the build and adds warnings in the appropriate documentation and configuration sections.
* schedulerpriorityaffinitysmp.h: Fix compilation error introduced by recent ↵Joel Sherrill2014-04-041-2/+6
| | | | changes
* privateenv.c: Remove unused variable warningJoel Sherrill2014-04-041-1/+0
|
* score: Add scheduler control to scheduler opsSebastian Huber2014-04-0480-380/+756
| | | | | Scheduler operations must be free of a global scheduler context to enable partitioned/clustered scheduling.
* score: Add and use Scheduler_simple_ControlSebastian Huber2014-04-046-18/+28
|
* score: Add and use Scheduler_EDF_ControlSebastian Huber2014-04-047-30/+45
|
* score: Delete superfluous fieldSebastian Huber2014-04-041-5/+0
|
* score: Include missing header fileSebastian Huber2014-04-041-5/+8
|
* score: Move declaration to end of fileSebastian Huber2014-04-041-7/+6
|
* pthreadimpl.h: Conditionalize thread affinity copyingJoel Sherrill2014-04-031-1/+1
|
* pthreadcreate.c: Fix bug where attr used instead of the_attrJoel Sherrill2014-04-031-14/+13
|
* pthread.c: Conditionalize thread affinity initializationJoel Sherrill2014-04-031-1/+1
|
* posix: Move affinity from thread to scheduler.Jennifer Averett2014-04-034-21/+28
|
* posix: Modified pthread init to use cpuset default.Jennifer Averett2014-04-031-12/+8
|
* rtems: Move affinity from thread to scheduler.Jennifer Averett2014-04-032-9/+9
|
* sapi: Add priority affinity smp scheduler.Jennifer Averett2014-04-031-0/+22
|
* score: Remove affinity element from thread.Jennifer Averett2014-04-032-14/+0
|
* score: Add priority affinity smp scheduler.Jennifer Averett2014-04-034-0/+230
|
* score: score: Add get/set affinity to Scheduler Framework.Jennifer Averett2014-04-0310-11/+192
|
* score: Move priority bit map to scheduler instanceSebastian Huber2014-04-0321-254/+334
| | | | | | Delete global variables _Priority_Major_bit_map and _Priority_Bit_map. This makes it possible to use multiple priority scheduler instances for example with clustered/partitioned scheduling on SMP.
* score: Rename Priority_bit_map_ControlSebastian Huber2014-04-0332-58/+58
| | | | Rename Priority_bit_map_Control in Priority_bit_map_Word.
* score: PR788: Add INTERNAL_ERROR_RESOURCE_IN_USESebastian Huber2014-04-033-2/+12
| | | | | | | | | | | | | | | Issue a fatal error in case a thread is deleted which still owns resources (e.g. a binary semaphore with priority inheritance or ceiling protocol). The resource count must be checked quite late since RTEMS task variable destructors, POSIX key destructors, POSIX cleanup handler, the Newlib thread termination extension or other thread termination extensions may release resources. In this context it would be quite difficult to return an error status to the caller. An alternative would be to place threads with a non-zero resource count not on the zombie chain. Thus we have a resource leak instead of a fatal error. The terminator thread can see this error if we return an RTEMS_RESOURCE_IN_USE status for the rtems_task_delete() for example.
* score: Move __log2table to separate fileSebastian Huber2014-04-013-21/+44
|
* ringbuf: Fix ISR lock initialization/destructionSebastian Huber2014-04-011-0/+6
|
* score: PR2172: _Thread_queue_Extract()Sebastian Huber2014-04-016-30/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add _Thread_queue_Extract_with_return_code(). On SMP this sequence in _Thread_queue_Process_timeout() was broken: [...] /* * After we enable interrupts here, a lot may happen in the * meantime, e.g. nested interrupts may release the resource that * times out here. So we enter _Thread_queue_Extract() * speculatively. Inside this function we check the actual status * under ISR disable protection. This ensures that exactly one * executing context performs the extract operation (other parties * may call _Thread_queue_Dequeue()). If this context won, then * we have a timeout. * * We can use the_thread_queue pointer here even if * the_thread->Wait.queue is already set to NULL since the extract * operation will only use the thread queue discipline to select * the right extract operation. The timeout status is set during * thread queue initialization. */ we_did_it = _Thread_queue_Extract( the_thread_queue, the_thread ); if ( we_did_it ) { the_thread->Wait.return_code = the_thread_queue->timeout_status; } [...] In case _Thread_queue_Extract() successfully extracted a thread, then this thread may start execution on a remote processor immediately and read the the_thread->Wait.return_code before we update it here with the timeout status. Thus it observes a successful operation even if it timed out.
* score: _Thread_queue_Extract_with_proxy()Sebastian Huber2014-03-312-5/+3
| | | | Drop the return status, since it is nowhere used.
* score: Delete CORE_mutex_Control::lockSebastian Huber2014-03-318-34/+16
| | | | | | | | The holder field is enough to determine if a mutex is locked or not. This leads also to better error status codes in case a rtems_semaphore_release() is done for a mutex without having the ownership.
* score: Delete CORE_mutex_Control::holder_idSebastian Huber2014-03-315-11/+8
| | | | We can use the holder pointer to get the identifier if necessary.
* score: Delete CORE_mutex_Control::blocked_countSebastian Huber2014-03-313-4/+0
|
* score: Do not reset resource count during restartSebastian Huber2014-03-311-1/+0
| | | | | | | This fixes an integer underflow problem in case resources are released after a thread restart. Add new test sptests/spthreadlife01.
* score: PR2152: Use allocator mutex for objectsSebastian Huber2014-03-3162-317/+417
| | | | | Use allocator mutex for objects allocate/free. This prevents that the thread dispatch latency depends on the workspace/heap fragmentation.
* score: Use thread life protection for API mutexesSebastian Huber2014-03-313-36/+46
| | | | | This prevents that asynchronous thread deletion can lead to an unusable allocator or once mutex.
* score: Relax Giant lock usage for API mutexesSebastian Huber2014-03-313-5/+6
| | | | | It is no longer necessary to protect the workspace allocations with the Giant lock due to the thread life cycle re-implementation.
* score: Thread life cycle re-implementationSebastian Huber2014-03-3123-308/+623
| | | | | | | | | | | | | | | | | | | The thread deletion is now supported on SMP. This change fixes the following PRs: PR1814: SMP race condition between stack free and dispatch PR2035: psxcancel reveals NULL pointer access in _Thread_queue_Extract() The POSIX cleanup handler are now called in the right context (should be called in the context of the terminating thread). http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html Add a user extension the reflects a thread termination event. This is used to reclaim the Newlib reentrancy structure (may use file operations), the POSIX cleanup handlers and the POSIX key destructors.
* score: Replace _Thread_Reset()Sebastian Huber2014-03-311-23/+18
| | | | | Replace _Thread_Reset() with _Thread_Start_life_change(). This function can be later used for the _Thread_Close() implementation.
* score: Add parameter to _Thread_Restart()Sebastian Huber2014-03-313-12/+11
| | | | | The executing thread will be later used for a common implementation with _Thread_Close().
* score: Fix thread restart extensions contextSebastian Huber2014-03-313-7/+17
| | | | | Run the thread restart extensions in the context of the restarted thread. Run them with thread dispatching enabled.
* score: Reduce _Thread_Reset() parametersSebastian Huber2014-03-311-19/+7
| | | | | Move thread entry parameters out of _Thread_Reset() to enable re-usablity of this function.
* score: Move _Thread_Reset() and make staticSebastian Huber2014-03-314-67/+29
|
* score: Use thread action for thread restartSebastian Huber2014-03-316-45/+79
| | | | | The thread restart is now supported on SMP. New test smptests/smpthreadlife01.
* score: Delete post-switch API extensionsSebastian Huber2014-03-313-76/+0
| | | | Use thread post-switch actions instead.
* posix: Use thread action for signalsSebastian Huber2014-03-317-23/+28
|
* rtems: Use thread action for signalsSebastian Huber2014-03-316-10/+36
|
* score: Add thread actionsSebastian Huber2014-03-314-0/+161
| | | | | | | | | | Thread actions are the building block for efficient implementation of - Classic signals delivery, - POSIX signals delivery, - thread restart notification, - thread delete notification, - forced thread migration on SMP configurations, and - the Multiprocessor Resource Sharing Protocol (MrsP).
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-18 11:06:56 +0000