Lines Matching refs:requests
256 &i915_request_timeline(rq)->requests));
260 * We only loosely track inflight requests across preemption,
307 tmp = list_first_entry(&tl->requests, typeof(*tmp), link);
370 * requests that we have unsubmitted from HW, but left running
421 list_move_tail(&request->sched.link, &engine->active.requests);
560 list_for_each_entry_safe(rq, rn, &tl->requests, link)
570 if (list_empty(&tl->requests))
577 rq = list_first_entry(&tl->requests, typeof(*rq), link);
586 rq = list_last_entry(&tl->requests, typeof(*rq), link);
589 /* Retire our old requests in the hope that we free some */
641 * We use RCU to look up requests in flight. The lookups may
774 rq = list_first_entry(&tl->requests, typeof(*rq), link);
775 if (!list_is_last(&rq->link, &tl->requests))
808 &rcu_dereference(signal->timeline)->requests)) {
1008 * Requests on the same timeline are explicitly ordered, along
1010 * that requests are submitted in-order through each ring.
1061 /* Submit both requests at the same time */
1149 * request must wait for it to complete (either CPU or in hw, requests
1153 * request must wait for outstanding read requests to complete.
1268 list_add_tail(&rq->link, &timeline->requests);
1398 * or contexts, retiring a bunch of requests is mostly list management
1453 * We don't track the timestamps around requests, nor the average
1456 * order in which requests are executed by the context and so we can
1465 * When waiting for high frequency requests, e.g. during synchronous
Indexes created Wed Oct 15 07:09:58 GMT 2025