Changes between Version 60 and Version 61 of Developer/SMP

Timestamp:

04/15/14 19:54:29 (10 years ago)

Author:

Mayes

Comment:

/* Status */

Developer/SMP

@@ -11 +11 @@
 
 TBD: Insert table of status per task here with links to task
+
+{| border="1" style="margin: 1em auto 1em auto;text-align: center;"
+|+
+|-
+|'''Task Name''' || '''Status Summary''' 
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Low-Level_Start Low Level Start] || Incomplete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Processor_Affinity Processor Affinity] || Ongoing
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Atomic_Operations Atomic Operations] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#SMP_Locks SMP Locks] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#ISR_Locks ISR Locks] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Giant_Lock_vs._Fine_Grained_Locking Giant Lock vs Fine Grained Locking] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Watchdog_Handler Watchdog Handler] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Per-CPU_Control Per-CPU Control] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Interrupt_Support Interrupt Support] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Global_Scheduler Global Scheduler] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Clustered_Scheduling Clustered Scheduling] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Task_Variables Task Variables] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Non-Preempt_Mode_for_Mutual_Exclusion Non-Preempt Mode for Mutual Exclusion] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Thread_Restart Thread Restart] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Thread_Delete Thread Delete] || Complete
+|-
+| [http://www.rtems.org/wiki/index.php/SMP#Semaphores_and_Mutexes Semaphores and Mutexes] || Complete
+|-
+|}
 =  Requirements  =
 
@@ -1466 +1505 @@
 that the time of disabled interrupts increases.  The FIFO thread queue
 operations are trivial doubly-linked list operations.  The priority thread
-queue operations execute in a worst-case time which depends only on the maximum
-number of priorities.
-=  Post-Switch Actions  =
-
-==  Reason  ==
-
-
-Currently threads are assigned to processors for execution by the scheduler
-responsible for this thread.  It is unknown to the system when a thread
-actually starts or terminates execution on its assigned processor.  The
-termination event is important for the following features
- *  explicit thread migration, e.g. if a thread should move from one scheduler domain to another,
- *  thread deletion, since the thread stack is in use until the thread stopped execution, or
- *  restart of threads executing on a remote processor.
-==  RTEMS API Changes  ==
-
-
-None.
-==  Implementation  ==
-
-
-One approach to do post-switch actions could be to spin on the per-processor
-variable reflecting the executing thread.  This has at least two problems
-# it doesn't work if the executing thread wants to alter its own state, and
-# this spinning must be done with the scheduler lock held and interrupts disabled, this is a disaster for the interrupt latency,
-
-The proposed solution is to use an optional action handler which is active in
-case the thread execution termination matters.  In _Thread_Dispatch() we have
-already the post-switch extensions invoked after a thread switch.
-Unfortunately they execute after thread dispatching is enabled again and at
-this point the current processor may have already changed due to thread
-migration requested by an interrupt.
-
-We need a context which executes right after the thread context switch on the
-current processor, but without the per-processor lock acquired (to prevent lock
-order reversal problems and keep the interrupt latency small).
+queue operations execute in a worst-case t