Lines Matching full:scheduling

4 Core Scheduling
6 Core scheduling support allows userspace to define groups of tasks that can
19 scheduling is a scheduler feature that can mitigate some (not all) cross-HT
24 world workloads. In theory, core scheduling aims to perform at least as good as
26 not always: as synchronizing scheduling decisions across 2 or more CPUs in a
29 scheduling to perform more poorly compared to SMT-disabled, where N_CPUS is the
34 Core scheduling support is enabled via the ``CONFIG_SCHED_CORE`` config option.
38 doing its best to satisfy the system's scheduling requirements.
40 Core scheduling can be enabled via the ``PR_SCHED_CORE`` prctl interface.
41 This interface provides support for the creation of core scheduling groups, as
91 scheduling group and share it with already running tasks.
151 Core scheduling maintains trust relationships amongst groups of tasks by
153 When a system with core scheduling boots, all tasks are considered to trust
164 Limitations of core-scheduling
166 Core scheduling tries to guarantee that only trusted tasks run concurrently on a
173 Core scheduling selects only trusted tasks to run together. IPI is used to notify
181 Open cross-HT issues that core scheduling does not solve
185 Core scheduling cannot protect against MDS attacks between the siblings
194 Core scheduling cannot protect against an L1TF guest attacker exploiting a
211 Unfortunately, core scheduling does not protect kernel contexts running on
219 The main use case for Core scheduling is mitigating the cross-HT vulnerabilities
224 - Gang scheduling: Requirements for a group of tasks that needs to be scheduled
225   together could also be realized using core scheduling. One example is vCPUs of