Lines Matching refs:semaphores
556 * Are we using semaphores when the gpu is already saturated?
558 * Using semaphores incurs a cost in having the GPU poll a
566 * system is overloaded and using semaphores at this time only
568 * further use of semaphores until we are idle again, whence we
571 if (request->sched.semaphores &&
573 engine->saturated |= request->sched.semaphores;
646 if (request->sched.semaphores && i915_request_started(request))
647 request->sched.semaphores = 0;
1020 return rq->sched.semaphores | READ_ONCE(rq->engine->saturated);
1114 to->sched.semaphores |= mask;
1172 * Ensure both start together [after all semaphores in signal]
1213 * The downside of using semaphores is that we lose metadata passing
1498 * precludes optimising to use semaphores serialisation of a single