Lines Matching refs:run
20 (\obj{SCO}), and threads cannot run unless they are bound to, or receive a
112 thread to run for more than $b$ out of every $p$ microseconds. However, $\frac{b}{p}$ does not
200 on a single node. A scheduling control cap for each node is provided to the initial task at run
201 time. Threads run on the node that their scheduling context is configured for. Scheduling context
255 Passive threads will run on the CPU node that the scheduling context was configured with, and will
272 the highest priority thread will always run, however it is up to the system
309 null capability, the kernel will pause the thread and it will not run again.
314 Standard exception handlers can be passive, in which case they will run on the
319 Timeout faults are raised when a thread attempts to run but has no available
607 A thread belongs to exactly one domain, and will only run when that domain
627 to provide a thread with this ability to run in higher privilege mode. See the section on
662 to run in such a way as to violate any kernel properties. For example, it is not possible to