| 390 | |
| 391 | At any one time a thread belongs to exactly one dispatching domain. There will |
| 392 | be no scheduling hierarchies and no intersections between dispatching domains. |
| 393 | If no dispatching domain is explicitly specified, then it will inherit the one |
| 394 | from the executing context to support external code that is not aware of |
| 395 | clustered scheduling. This inheritance feature is erroneous and static checks |
| 396 | should be made on the program code and link directives to prevent it from |
| 397 | happening in this study project. |