Lines Matching refs:sibling

105 During a schedule() event on any sibling of a core, the highest priority task on
106 the sibling's core is picked and assigned to the sibling calling schedule(), if
107 the sibling has the task enqueued. For rest of the siblings in the core,
114 switch to the new task immediately. If an idle task is selected for a sibling,
115 then the sibling is considered to be in a `forced idle` state. I.e., it may
127 task.  If a sibling does not have a trusted task to run, it will be forced idle
131 the sibling to force it into idle. This results in 4 cases which need to be
189 sibling. Such attacks are possible for any combination of sibling CPU modes
212 sibling hyperthreads from one another. Prototypes of mitigations have been posted