summaryrefslogtreecommitdiffstats
path: root/cpukit (follow)
Commit message (Collapse)AuthorAgeFilesLines
* configure: Paravirtualization for all targetsSebastian Huber2014-05-081-7/+3
| | | | Virtual machines with paravirtualization exist not only on x86.
* rtems: Fix ASR SMP supportSebastian Huber2014-05-072-3/+24
| | | | Initialize the ISR lock only once and destroy it properly.
* score: Fix SMP startupSebastian Huber2014-05-071-1/+3
|
* score: Implement forced thread migrationSebastian Huber2014-05-0729-137/+403
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: Delete _SMP_Test_message_default_handlerSebastian Huber2014-05-071-7/+1
| | | | | A default handler is not necessary. The test message sender must ensure that a handler is installed.
* score: DocumentationSebastian Huber2014-05-072-4/+12
|
* posix: Fix POSIX keys initializationSebastian Huber2014-05-061-5/+5
| | | | | Always initialize the freechain. This prevents a NULL pointer access in case no initial key value pairs are defined.
* score: Use atomic operations for SMP messagesSebastian Huber2014-05-053-19/+15
|
* score: Add SMP test message handlerSebastian Huber2014-05-052-0/+36
| | | | | This handler can be used to test the inter-processor interrupt implementation.
* score: SMP_FATAL_SCHEDULER_WITHOUT_PROCESSORSSebastian Huber2014-05-055-23/+29
| | | | | 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().
* score: Fix TLS size usageSebastian Huber2014-05-053-7/+11
|
* score: TypoSebastian Huber2014-04-301-1/+1
|
* score: Statically initialize _ISR_Vector_tableSebastian Huber2014-04-2916-141/+26
|
* sapi: Report profiling only if enabled for testsSebastian Huber2014-04-291-0/+2
|
* score: Avoid copy and pasteSebastian Huber2014-04-281-19/+15
|
* sapi: Add profiling done messageSebastian Huber2014-04-281-0/+6
|
* sapi: Add arithmetic means to XML profiling reportSebastian Huber2014-04-281-9/+62
|
* sparc: Add _CPU_Get_current_per_CPU_control()Sebastian Huber2014-04-282-33/+36
| | | | | | | | | | | | | | | | Use register g6 for the per-CPU control of the current processor. The register g6 is reserved for the operating system by the SPARC ABI. On Linux register g6 is used for a similar purpose with the same method since 1996. The register g6 must be initialized during system startup and then must remain unchanged. Since the per-CPU control is used in all critical sections of the operating system, this is a performance optimization for the operating system core procedures. An additional benefit is that the low-level context switch and interrupt processing code is now identical on non-SMP and SMP configurations.
* sparc: Optimize context switchSebastian Huber2014-04-282-51/+48
| | | | | | The registers g2 through g4 are reserved for applications. GCC uses them as volatile registers by default. So they are treated like volatile registers in RTEMS as well.
* score: Add _CPU_Get_current_per_CPU_control()Sebastian Huber2014-04-282-3/+25
| | | | | | | | | Add optional method _CPU_Get_current_per_CPU_control() to obtain the per-CPU control of the current processor. This is optional. Not every CPU port needs this. It is only an optional optimization variant. In case this macro is undefined, the default implementation using the current processor index will be used.
* rtems: Account for the network semaphore.Chris Johns2014-04-271-1/+8
|
* sapi: Fix condef.h compile error for disabled network configuration.Jennifer Averett2014-04-251-0/+2
| | | | Added define for CONFIGURE_SEMAPHORES_FOR_NFS when networking disabled.
* libfs/rfs: Fix the fstime failures for the RFS file system.Chris Johns2014-04-252-12/+22
|
* rtems: Account for file system semaphores.Chris Johns2014-04-251-2/+32
| | | | Add support to account for the semaphores used by the file systems.
* mpci.c: Now compiles againJoel Sherrill2014-04-221-1/+3
|
* score: Use common names for per-CPU variablesSebastian Huber2014-04-2215-183/+183
| | | | | | | | | | | | | | | | Use "cpu" for an arbitrary Per_CPU_Control variable. Use "cpu_self" for the Per_CPU_Control of the current processor. Use "cpu_index" for an arbitrary processor index. Use "cpu_index_self" for the processor index of the current processor. Use "cpu_count" for the processor count obtained via _SMP_Get_processor_count(). Use "cpu_max" for the processor maximum obtained by rtems_configuration_get_maximum_processors().
* score: Fix warningSebastian Huber2014-04-221-2/+0
|
* score: Delete superfluous assignmentsSebastian Huber2014-04-221-7/+0
| | | | These values are already zero initialized by C run-time setup.
* score: Simplify Giant lockSebastian Huber2014-04-221-9/+7
|
* score: Use _Per_CPU_Get_snapshot()Sebastian Huber2014-04-221-1/+1
|
* score: Clarify TLS supportSebastian Huber2014-04-174-5/+5
|
* doc: rtems_task_set_scheduler()Sebastian Huber2014-04-171-0/+3
|
* doc: rtems_get_processor_count()Sebastian Huber2014-04-171-8/+5
|
* sapi: Fix CONFIGURE_UNLIMITED_OBJECTSSebastian Huber2014-04-171-6/+8
| | | | POSIX keys and key value pairs support now the unlimited option.
* sapi: Error case for CONFIGURE_UNLIMITED_OBJECTSSebastian Huber2014-04-171-0/+6
|
* rtems: Add const qualifierSebastian Huber2014-04-162-6/+6
|
* score: DocumentationSebastian Huber2014-04-161-0/+5
|
* score: Critical fix for SMPSebastian Huber2014-04-163-18/+21
| | | | | | The _Scheduler_SMP_Allocate_processor() and _Thread_Dispatch() exchange information without locks. Make sure we use the right load/store ordering.
* score: Add clustered/partitioned schedulingSebastian Huber2014-04-1520-91/+486
| | | | | | | | | | | | | | | Clustered/partitioned scheduling helps to control the worst-case latencies in the system. The goal is to reduce the amount of shared state in the system and thus prevention of lock contention. Modern multi-processor systems tend to have several layers of data and instruction caches. With clustered/partitioned scheduling it is possible to honour the cache topology of a system and thus avoid expensive cache synchronization traffic. We have clustered scheduling in case the set of processors of a system is partitioned into non-empty pairwise-disjoint subsets. These subsets are called clusters. Clusters with a cardinality of one are partitions. Each cluster is owned by exactly one scheduler instance.
* rtems: Add task get/set schedulerSebastian Huber2014-04-155-0/+180
|
* rtems: Add scheduler get processorsSebastian Huber2014-04-154-0/+92
|
* rtems: Add scheduler identificationSebastian Huber2014-04-156-1/+85
|
* score: Add scheduler nameSebastian Huber2014-04-153-22/+70
|
* score: Task get/set affinitySebastian Huber2014-04-159-90/+243
| | | | | 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-1525-419/+200
| | | | | | | | | | | 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.
* score: Static scheduler configurationSebastian Huber2014-04-1579-662/+867
| | | | | | Do not allocate the scheduler control structures from the workspace. This is a preparation step for configuration of clustered/partitioned schedulers on SMP.
* score: Add and use RTEMS_ZERO_LENGTH_ARRAYSebastian Huber2014-04-153-2/+9
|
* capture: Use ISR lock for SMP supportSebastian Huber2014-04-141-71/+72
|
* score: SMP initialization changesSebastian Huber2014-04-147-19/+85
| | | | | | | | | | | | | | | | | Add and use _CPU_SMP_Start_processor(). Add and use _CPU_SMP_Finalize_initialization(). This makes most _CPU_SMP_Initialize() functions a bit simpler since we can calculate the minimum value of the count of processors requested by the application configuration and the count of physically or virtually available processors in the high-level code. The CPU port has now the ability to signal a processor start failure. With the support for clustered/partitioned scheduling the presence of particular processors can be configured to be optional or mandatory. There will be a fatal error only in case mandatory processors are not present. The CPU port may use a timeout to monitor the start of a processor.
* score: Add _Per_CPU_Get_snapshot()Sebastian Huber2014-04-141-3/+12
|