CVS difference for ai12s/ai12-0048-1.txt

Differences between 1.2 and version 1.3
Log of other versions for file ai12s/ai12-0048-1.txt

--- ai12s/ai12-0048-1.txt	2012/12/05 04:18:26	1.2
+++ ai12s/ai12-0048-1.txt	2013/01/04 04:38:04	1.3
@@ -1,5 +1,7 @@
-!standard D.16.1(30/3)                               12-12-03    AI12-0048-1/01
+!standard D.16.1(30/3)                               13-01-03    AI12-0048-1/02
 !class binding interpretation 12-11-29
+!status Amendment 202x 13-01-03
+!status ARG Approved 8-0-2  12-12-08
 !status work item 12-11-29
 !status received 12-04-09
 !priority Low
@@ -15,7 +17,7 @@
 
 The language does not appear to say anything about which tasks are allowed to run on which
 CPUs of a multiprocessor in the absence of using any D.16 or D.16.1 facilities. Some real-time
-models map each task to  a single CPU by default. This seems as if it could cause unbounded
+models map each task to a single CPU by default. This seems as if it could cause unbounded
 priority inversion.
 
 For instance, consider an implementation which mapped all tasks of a particular task type to
@@ -43,11 +45,11 @@
 
 Add after D.16.1(30/3): [in Implementation Requirements]
 
-For all tasks that belong to the system dispatching domain, unless a task T has been assigned to a
-specific CPU, T can execute on all CPUs that belong to the system dispatching domain of T.
+Any task that belongs to the system dispatching domain can execute on any CPU within that domain,
+unless the assignment of the task has been specified.
 
 AARM Reason: This ensures that priorities and deadlines are respected within the system dispatching
-domain. There is no such guarentee between multiple domains.
+domain. There is no such guarentee between different domains.
 
 We only need to talk about the system dispatching domain here, because Assign_Task and Set_CPU
 already have such wording for tasks that are assigned explicitly to a dispatching domain and
@@ -92,6 +94,17 @@
 domain eliminates any protection against priority inversion; we assume that users are
 aware of these possibilities and have taken steps to ensure that nothing bad happens
 in that case.
+
+!corrigendum D.16.1(30/3)
+
+@dinsa
+The implementation shall perform the operations Assign_Task, Set_CPU, Get_CPU and
+Delay_Until_And_Set_CPU atomically with respect to any of these operations on the same
+dispatching_domain, processor or task.
+@dinst
+Any task that belongs to the system dispatching domain can execute on any CPU within that
+domain, unless the assignment of the task has been specified.
+
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent