Lines Matching defs:possible
399 * XXX entirely possible to selectively enable cores, don't bother for now.
613 * Additionally it is possible to be ->on_rq but still be considered not
624 * [ The astute reader will observe that it is possible for two tasks on one
2819 * Because this is called with p->pi_lock held, it is not possible
3549 enum { cpuset, possible, fail } state = cpuset;
3580 state = possible;
3584 case possible:
3917 * it is possible for select_idle_siblings() to stack a number
4302 * be possible to, falsely, observe p->on_rq == 0 and get stuck
4328 * possible to, falsely, observe p->on_cpu == 0.
4438 * possible to, falsely, observe p->on_rq == 0.
5170 * In that case it would be possible for __schedule() to interleave
5381 * kernel thread and not issued an IPI. It is therefore possible to
6961 * Its possible to race where after we check owner->on_rq
6973 * It's possible we interleave with mutex_unlock like:
7040 * called on the nearest possible occasion:
9422 /* Wait for possible concurrent references to cfs_rqs complete: */
10676 * following possible states:
10762 * happens first. mm_cid_fixup_cpus_to_task() walks through the possible
10781 /* Adjust the maximum CIDs to +25% limited by the number of possible CPUs */