summaryrefslogtreecommitdiffstats
path: root/cpukit/score (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 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-0320-251/+330
| | | | | | 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-032-1/+10
| | | | | | | | | | | | | | | 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
|
* 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-315-24/+9
| | | | | | | | 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-314-9/+1
| | | | 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-318-49/+204
| | | | | 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-312-4/+5
| | | | | 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-3111-190/+511
| | | | | | | | | | | | | | | | | | | 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-312-11/+10
| | | | | The executing thread will be later used for a common implementation with _Thread_Close().
* score: Fix thread restart extensions contextSebastian Huber2014-03-312-6/+7
| | | | | 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-315-36/+78
| | | | | 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.
* 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).
* score: Add and use thread get/set CPU functionsSebastian Huber2014-03-314-8/+34
|
* score: Add _Scheduler_Change_priority_if_higher()Sebastian Huber2014-03-312-9/+38
| | | | Add _Scheduler_Set_priority_if_higher().
* score: Add _Scheduler_Highest_priority_of_two()Sebastian Huber2014-03-311-7/+29
| | | | | | Use inline functions instead of macros for _Scheduler_Is_priority_lower_than() and _Scheduler_Is_priority_higher_than().
* score: PR2151: _Thread_queue_Extract_with_proxy()Sebastian Huber2014-03-311-23/+24
| | | | Avoid NULL pointer access.
* score: Add per-CPU state functionSebastian Huber2014-03-312-1/+41
| | | | | Add _Per_CPU_State_wait_for_ready_to_start_multitasking(). Add new fatal SMP error SMP_FATAL_SHUTDOWN_EARLY.
* score: PR2174: Add workaroundSebastian Huber2014-03-252-0/+11
| | | | | Add _Scheduler_FIXME_thread_priority_queues_are_broken to prevent thread priority queues in case an EDF scheduler is used.
* score: Delete _Watchdog_Report()Sebastian Huber2014-03-254-132/+1
| | | | | | | Delete _Watchdog_Report_chain(). These two functions use printk() with thread dispatching and interrupts disabled. So they are pretty useless in real applications. They are not part of the application APIs. They are only used in one test and do nothing useful in this test.
* score: Fix heap protectionSebastian Huber2014-03-251-7/+21
| | | | Partially revert commit 2a713e3b944625c45154f0ea7f5703e918de758.
* score: _Heap_Protection_set_delayed_free_fractionSebastian Huber2014-03-246-22/+38
| | | | | Add and use _Heap_Protection_set_delayed_free_fraction(). This makes it possible to avoid a dependency on _Thread_Dispatch_is_enabled().
* score: Start thread dispatch profiling laterSebastian Huber2014-03-241-3/+4
| | | | We are not interested in the sequential boot time.
* score: Delete _Thread_Internal_free()Sebastian Huber2014-03-241-11/+0
|
* score: _Debug_Is_thread_dispatching_allowed()Sebastian Huber2014-03-241-2/+1
| | | | Do not check ISR level in _Debug_Is_thread_dispatching_allowed().
* score: Delete unused STATES_ALL_SETSebastian Huber2014-03-241-2/+0
|
* score: Set name before object is made publicSebastian Huber2014-03-241-10/+10
|
* score: Unify pthread and gxx_wrapper once and move to score.Christian Mauderer2014-03-214-0/+110
|
* Change all references of rtems.com to rtems.org.Chris Johns2014-03-21542-542/+542
|
* score: Add _Assert_Not_reached()Sebastian Huber2014-03-191-0/+5
|
* score: Add _Debug_Is_owner_of_allocator()Sebastian Huber2014-03-193-0/+46
|
* score: Delete _Assert_Owner_of_giant()Sebastian Huber2014-03-193-13/+13
| | | | | Add _Debug_Is_owner_of_giant(). This makes it possible to assert the opposite.
* score: Delete _Assert_Thread_dispatching_repressedSebastian Huber2014-03-194-14/+12
| | | | | | | | Add _Debug_Is_thread_dispatching_allowed(). This makes it possible to assert the opposite. Use _ISR_Disable_without_giant()/_ISR_Enable_without_giant() to avoid misleading secondary assertion failures.
* posix: Use interal mutex for once implementationSebastian Huber2014-03-191-0/+12
| | | | | | Enable pthread_once() for all configurations. The pthread_once() function is one means to initialize POSIX keys. Another use case is the C++ support.
* score: Make _ISR_Enable_without_giant() availableSebastian Huber2014-03-181-4/+0
| | | | Make _ISR_Enable_without_giant() available for non-SMP configurations.
* score: Use only next field for chain on/offSebastian Huber2014-03-171-6/+6
| | | | | It is sufficient to use one field for the chain on/off indication. The chain API functions are highly performance critical.
* score: Add include for uintptr_t definition.Daniel Cederman2014-03-171-0/+1
|
* arm: Add support for interrupt profilingSebastian Huber2014-03-141-0/+20
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-23 18:00:07 +0000