Lines Matching refs:requests
380 &i915_request_timeline(rq)->requests));
396 * We only loosely track inflight requests across preemption,
428 tmp = list_first_entry(&tl->requests, typeof(*tmp), link);
456 * requests, we know that only the currently executing request
617 * requests that we have unsubmitted from HW, but left running
829 list_for_each_entry_safe(rq, rn, &tl->requests, link)
850 if (list_empty(&tl->requests))
854 rq = list_first_entry(&tl->requests, typeof(*rq), link);
863 rq = list_last_entry(&tl->requests, typeof(*rq), link);
866 /* Retire our old requests in the hope that we free some */
910 * We use RCU to look up requests in flight. The lookups may
1010 list_add_tail_rcu(&rq->link, &tl->requests);
1039 rq = list_first_entry(&tl->requests, typeof(*rq), link);
1040 if (!list_is_last(&rq->link, &tl->requests))
1090 if (pos == &rcu_dereference(signal->timeline)->requests)
1271 /* Submit both requests at the same time */
1286 * run (consider that we submit 2 requests for the same context, where
1308 * was submitted in a chain of requests following another context
1531 * that requests are submitted in-order through each ring.
1594 * request must wait for it to complete (either CPU or in hw, requests
1598 * request must wait for outstanding read requests to complete.
1688 * The requests are supposed to be kept in order. However,
1755 * We do not order parallel submission requests on the timeline as each
1757 * rules for parallel requests are that they must be submitted in the
1910 * We don't track the timestamps around requests, nor the average
1913 * order in which requests are executed by the context and so we can
1922 * When waiting for high frequency requests, e.g. during synchronous