summaryrefslogtreecommitdiffstats
path: root/cpukit/rtems/include/rtems/rtems/tasks.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove make preinstallChris Johns2018-01-251-716/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* rtems: Add rtems_scheduler_ident_by_processor_setSebastian Huber2017-07-111-0/+25
| | | | Update #3070.
* rtems: Add rtems_scheduler_ident_by_processor()Sebastian Huber2017-07-111-0/+17
| | | | Update #3069.
* rtems: Fix RTEMS_MAXIMUM_PRIORITY defineSebastian Huber2017-02-011-1/+1
| | | | | Cast the internal PRIORITY_MAXIMUM to the right type for a Classic API task priority to avoid integer conversion warnings.
* Remove obsolete __RTEMS_HAVE_SYS_CPUSET_H__Joel Sherrill2017-01-111-4/+0
|
* rtems: Add scheduler processor add/removeSebastian Huber2016-11-101-4/+53
| | | | Update #2797.
* score: Simplify _Scheduler_Get_by_id()Sebastian Huber2016-11-091-2/+0
| | | | | | | | | | Avoid dead code in non-SMP configurations. Return scheduler identifier independent of the current processor count of the scheduler via rtems_scheduler_ident(), since this value may change during run-time. Check the processor count in _Scheduler_Set() under scheduler lock protection. Update #2797.
* rtems: Add rtems_task_iterate()Sebastian Huber2016-11-021-0/+32
| | | | Update #2423.
* rtems: Add rtems_task_get_priority()Sebastian Huber2016-09-211-0/+29
| | | | | Update #2556. Update #2784.
* rtems: Fix rtems_task_set_scheduler() APISebastian Huber2016-07-011-7/+16
| | | | | | | | | | | Task priorities are only valid within a scheduler instance. The rtems_task_set_scheduler() directive moves a task from one scheduler instance to another using the current priority of the thread. However, the current task priority of the source scheduler instance is undefined in the target scheduler instance. Add a third parameter to specify the priority. Close #2749.
* score: Change Priority_Control to 64-bitSebastian Huber2016-06-241-1/+1
| | | | | | | | A 32-bit Priority_Control limits the uptime to 49 days with a 1ms clock tick in case the EDF scheduler is used. Increase it to 64-bit to enable proper operation of the EDF scheduler, Close 2173.
* score: Add per scheduler instance maximum prioritySebastian Huber2016-05-201-0/+1
| | | | | | | | | | | The priority values are only valid within a scheduler instance. Thus, the maximum priority value must be defined per scheduler instance. The first scheduler instance defines PRIORITY_MAXIMUM. This implies that RTEMS_MAXIMUM_PRIORITY and POSIX_SCHEDULER_MAXIMUM_PRIORITY are only valid for threads of the first scheduler instance. Further API/implementation changes are necessary to fix this. Update #2556.
* rtems: Remove task variablesSebastian Huber2016-05-041-46/+0
| | | | | Update #2494. Update #2555.
* Use linker set for Classic User Tasks initSebastian Huber2016-02-031-9/+0
| | | | Update #2408.
* api: Remove deprecated NotepadsAun-Ali Zaidi2015-12-241-98/+0
| | | | | | | | | | | | | | | | | | | | | | | Notepads where a feature of RTEMS' tasks that simply functioned in the same way as POSIX keys or threaded local storage (TLS). They were introduced well before per task variables, which are also deprecated, and were barely used in favor of their POSIX alternatives. In addition to their scarce usage, Notepads took up unnecessary memory. For each task: - 16 32-bit integers were allocated. - A total of 64 bytes per task per thread. This is especially critical in low memory and safety-critical applications. They are also defined as uint32_t, and therefore are not guaranteed to hold a pointer. Lastly, they are not portable solutions for SMP and uniprocessor systems, like POSIX keys and TLS. updates #2493.
* basdefs.h: Add and use RTEMS_DEPRECATEDSebastian Huber2015-10-261-6/+6
|
* cpukit: deprecate task variables. closes #2293.Gedare Bloom2015-03-101-3/+9
|
* cpukit: deprecate notepadsGedare Bloom2015-03-101-3/+9
| | | | | | | | | | | | | | | Deprecate Classic API Notepads. Mark task_set/get_note() with the deprecated attribute, and also mark the notepads field. Replace disable with enable option for notepads in confdefs.h, and make notepads disabled by default. The previous option CONFIGURE_DISABLE_CLASSIC_API_NOTEPADS is now unused and will emit a compile-time warning. A new option CONFIGURE_ENABLE_CLASSIC_API_NOTEPADS is available to turn on notepads, but it also will emit a compile-time warning to indicate that notepads are deprecated. Closes #2265
* score: _Scheduler_Set_affinity()Sebastian Huber2014-06-021-0/+11
| | | | | Do not change the scheduler with this function. Documentation. Coding style.
* rtems: Clarify task set/get scheduler parametersSebastian Huber2014-05-201-6/+6
|
* score: Implement forced thread migrationSebastian Huber2014-05-071-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current implementation of task migration in RTEMS has some implications with respect to the interrupt latency. It is crucial to preserve the system invariant that a task can execute on at most one processor in the system at a time. This is accomplished with a boolean indicator in the task context. The processor architecture specific low-level task context switch code will mark that a task context is no longer executing and waits that the heir context stopped execution before it restores the heir context and resumes execution of the heir task. So there is one point in time in which a processor is without a task. This is essential to avoid cyclic dependencies in case multiple tasks migrate at once. Otherwise some supervising entity is necessary to prevent life-locks. Such a global supervisor would lead to scalability problems so this approach is not used. Currently the thread dispatch is performed with interrupts disabled. So in case the heir task is currently executing on another processor then this prolongs the time of disabled interrupts since one processor has to wait for another processor to make progress. It is difficult to avoid this issue with the interrupt latency since interrupts normally store the context of the interrupted task on its stack. In case a task is marked as not executing we must not use its task stack to store such an interrupt context. We cannot use the heir stack before it stopped execution on another processor. So if we enable interrupts during this transition we have to provide an alternative task independent stack for this time frame. This issue needs further investigation.
* score: SMP_FATAL_SCHEDULER_WITHOUT_PROCESSORSSebastian Huber2014-05-051-0/+2
| | | | | Avoid the SMP_FATAL_SCHEDULER_WITHOUT_PROCESSORS fatal error and make it a run-time error in rtems_scheduler_ident() and _Scheduler_Get_by_id().
* doc: rtems_task_set_scheduler()Sebastian Huber2014-04-171-0/+3
|
* rtems: Add const qualifierSebastian Huber2014-04-161-3/+3
|
* rtems: Add task get/set schedulerSebastian Huber2014-04-151-0/+35
|
* rtems: Add scheduler get processorsSebastian Huber2014-04-151-0/+24
|
* rtems: Add scheduler identificationSebastian Huber2014-04-151-0/+17
|
* score: Task get/set affinitySebastian Huber2014-04-151-24/+26
| | | | | Make rtems_task_get_affinity() and rtems_task_set_affinity() available on non-SMP configurations. Allow larger CPU sets.
* score: Simplify thread control initializationSebastian Huber2014-04-151-1/+1
| | | | | | | | | | | The thread control block contains fields that point to application configuration dependent memory areas, like the scheduler information, the API control blocks, the user extension context table, the RTEMS notepads and the Newlib re-entrancy support. Account for these areas in the configuration and avoid extra workspace allocations for these areas. This helps also to avoid heap fragementation and reduces the per thread memory due to a reduced heap allocation overhead.
* Disable per task variables when SMP is enabledJoel Sherrill2014-04-041-5/+9
| | | | | | 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.
* rtems: Use thread action for signalsSebastian Huber2014-03-311-0/+6
|
* Change all references of rtems.com to rtems.org.Chris Johns2014-03-211-1/+1
|
* Remove trailing whitespace in previous patchesJennifer Averett2014-03-071-11/+11
|
* rtems: Add Classic API get and set affinity methods.Jennifer Averett2014-03-071-0/+45
| | | | | | | Add the following methods: + rtems_task_get_affinity + rtems_task_set_affinity
* score: Create states implementation headerSebastian Huber2013-07-261-1/+0
| | | | | | Move implementation specific parts of states.h and states.inl into new header file statesimpl.h. The states.h contains now only the application visible API.
* rtems: Create tasks implementation headerSebastian Huber2013-07-231-79/+28
| | | | | | Move implementation specific parts of tasks.h and tasks.inl into new header file tasksimpl.h. The tasks.h contains now only the application visible API.
* rtems: Doxygen Clean Up Task #1Ayush Awasthi2013-01-041-134/+137
|
* Header File Doxygen Enhancement Task #7Mathew Kallada2012-12-281-0/+2
|
* misc rtems: Clean up Doxygen GCI Task #8Mathew Kallada2012-12-081-20/+24
| | | | http://www.google-melange.com/gci/task/view/google/gci2012/8024203
* rtems misc: Clean up Doxygen GCI Task #5Mathew Kallada2012-12-051-8/+12
| | | | http://www.google-melange.com/gci/task/view/google/gci2012/8015207
* rtems misc: Clean up Doxygen GCI Task #7Alex Ivanov2012-12-051-2/+9
| | | | http://www.google-melange.com/gci/task/view/google/gci2012/7950206
* rtems misc: Clean up Doxygen GCI Task #6Alex Ivanov2012-12-051-10/+30
| | | | http://www.google-melange.com/gci/task/view/google/gci2012/8019205
* rtems misc: Clean up Doxygen GCI Task #4Alex Ivanov2012-12-041-2/+16
| | | | http://www.google-melange.com/gci/task/view/google/gci2012/7950205
* cpukit: Clean up Doxygen #3 (GCI 2012)Alex Ivanov2012-12-031-3/+16
|
* score misc: Clean up Doxygen #14 (GCI 2012)Mathew Kallada2012-12-021-1/+8
| | | | | | | This patch is a task from GCI 2012 which improves the Doxygen comments in the RTEMS source. http://www.google-melange.com/gci/task/view/google/gci2012/8025204
* score misc: Clean up Doxygen #12 (GCI 2012)Alex Ivanov2012-12-021-10/+23
| | | | | | | This patch is a task from GCI 2012 which improves the Doxygen comments in the RTEMS source. http://www.google-melange.com/gci/task/view/google/gci2012/8025203
* rtems: Add system eventsSebastian Huber2012-10-301-0/+2
| | | | | | | System events are similar to normal events. They offer a second set of events. These events are intended for internal RTEMS use and should not be used by applications (with the exception of the transient system event).
* rtems: Reusable event implementationSebastian Huber2012-10-301-3/+3
| | | | Change event implementation to enable reuse for system events.
* rtems: Remove unused event_condition memberSebastian Huber2012-10-301-2/+0
|
* Remove All CVS Id Strings Possible Using a ScriptJoel Sherrill2012-05-111-2/+0
| | | | | | | | | | | | Script does what is expected and tries to do it as smartly as possible. + remove occurrences of two blank comment lines next to each other after Id string line removed. + remove entire comment blocks which only exited to contain CVS Ids + If the processing left a blank line at the top of a file, it was removed.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-14 05:30:12 +0000