Lines Matching full:siblings

100 siblings of a core such that all the selected tasks running on a core are
107 the sibling has the task enqueued. For rest of the siblings in the core,
112 Once a task has been selected for all the siblings in the core, an IPI is sent to
113 siblings for whom a new task was selected. Siblings on receiving the IPI will
125 siblings could be forced to select a lower priority task if the highest
157 and are considered system-wide trusted. The forced-idling of siblings running
174 the siblings to switch to the new task. But there could be hardware delays in
176 cause an attacker task to start running on a CPU before its siblings receive the
177 IPI. Even though cache is flushed on entry to user mode, victim tasks on siblings
185 Core scheduling cannot protect against MDS attacks between the siblings
187 siblings run tasks which trust each other, when the kernel is executing