Loading...
1/*
2 * Copyright © 2008-2018 Intel Corporation
3 *
4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
6 * to deal in the Software without restriction, including without limitation
7 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 * and/or sell copies of the Software, and to permit persons to whom the
9 * Software is furnished to do so, subject to the following conditions:
10 *
11 * The above copyright notice and this permission notice (including the next
12 * paragraph) shall be included in all copies or substantial portions of the
13 * Software.
14 *
15 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
18 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
20 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
21 * IN THE SOFTWARE.
22 *
23 */
24
25#ifndef I915_REQUEST_H
26#define I915_REQUEST_H
27
28#include <linux/dma-fence.h>
29#include <linux/hrtimer.h>
30#include <linux/irq_work.h>
31#include <linux/llist.h>
32#include <linux/lockdep.h>
33
34#include "gem/i915_gem_context_types.h"
35#include "gt/intel_context_types.h"
36#include "gt/intel_engine_types.h"
37#include "gt/intel_timeline_types.h"
38
39#include "i915_gem.h"
40#include "i915_scheduler.h"
41#include "i915_selftest.h"
42#include "i915_sw_fence.h"
43#include "i915_vma_resource.h"
44
45#include <uapi/drm/i915_drm.h>
46
47struct drm_file;
48struct drm_i915_gem_object;
49struct drm_printer;
50struct i915_deps;
51struct i915_request;
52
53#if IS_ENABLED(CONFIG_DRM_I915_CAPTURE_ERROR)
54struct i915_capture_list {
55 struct i915_vma_resource *vma_res;
56 struct i915_capture_list *next;
57};
58
59void i915_request_free_capture_list(struct i915_capture_list *capture);
60#else
61#define i915_request_free_capture_list(_a) do {} while (0)
62#endif
63
64#define RQ_TRACE(rq, fmt, ...) do { \
65 const struct i915_request *rq__ = (rq); \
66 ENGINE_TRACE(rq__->engine, "fence %llx:%lld, current %d " fmt, \
67 rq__->fence.context, rq__->fence.seqno, \
68 hwsp_seqno(rq__), ##__VA_ARGS__); \
69} while (0)
70
71enum {
72 /*
73 * I915_FENCE_FLAG_ACTIVE - this request is currently submitted to HW.
74 *
75 * Set by __i915_request_submit() on handing over to HW, and cleared
76 * by __i915_request_unsubmit() if we preempt this request.
77 *
78 * Finally cleared for consistency on retiring the request, when
79 * we know the HW is no longer running this request.
80 *
81 * See i915_request_is_active()
82 */
83 I915_FENCE_FLAG_ACTIVE = DMA_FENCE_FLAG_USER_BITS,
84
85 /*
86 * I915_FENCE_FLAG_PQUEUE - this request is ready for execution
87 *
88 * Using the scheduler, when a request is ready for execution it is put
89 * into the priority queue, and removed from that queue when transferred
90 * to the HW runlists. We want to track its membership within the
91 * priority queue so that we can easily check before rescheduling.
92 *
93 * See i915_request_in_priority_queue()
94 */
95 I915_FENCE_FLAG_PQUEUE,
96
97 /*
98 * I915_FENCE_FLAG_HOLD - this request is currently on hold
99 *
100 * This request has been suspended, pending an ongoing investigation.
101 */
102 I915_FENCE_FLAG_HOLD,
103
104 /*
105 * I915_FENCE_FLAG_INITIAL_BREADCRUMB - this request has the initial
106 * breadcrumb that marks the end of semaphore waits and start of the
107 * user payload.
108 */
109 I915_FENCE_FLAG_INITIAL_BREADCRUMB,
110
111 /*
112 * I915_FENCE_FLAG_SIGNAL - this request is currently on signal_list
113 *
114 * Internal bookkeeping used by the breadcrumb code to track when
115 * a request is on the various signal_list.
116 */
117 I915_FENCE_FLAG_SIGNAL,
118
119 /*
120 * I915_FENCE_FLAG_NOPREEMPT - this request should not be preempted
121 *
122 * The execution of some requests should not be interrupted. This is
123 * a sensitive operation as it makes the request super important,
124 * blocking other higher priority work. Abuse of this flag will
125 * lead to quality of service issues.
126 */
127 I915_FENCE_FLAG_NOPREEMPT,
128
129 /*
130 * I915_FENCE_FLAG_SENTINEL - this request should be last in the queue
131 *
132 * A high priority sentinel request may be submitted to clear the
133 * submission queue. As it will be the only request in-flight, upon
134 * execution all other active requests will have been preempted and
135 * unsubmitted. This preemptive pulse is used to re-evaluate the
136 * in-flight requests, particularly in cases where an active context
137 * is banned and those active requests need to be cancelled.
138 */
139 I915_FENCE_FLAG_SENTINEL,
140
141 /*
142 * I915_FENCE_FLAG_BOOST - upclock the gpu for this request
143 *
144 * Some requests are more important than others! In particular, a
145 * request that the user is waiting on is typically required for
146 * interactive latency, for which we want to minimise by upclocking
147 * the GPU. Here we track such boost requests on a per-request basis.
148 */
149 I915_FENCE_FLAG_BOOST,
150
151 /*
152 * I915_FENCE_FLAG_SUBMIT_PARALLEL - request with a context in a
153 * parent-child relationship (parallel submission, multi-lrc) should
154 * trigger a submission to the GuC rather than just moving the context
155 * tail.
156 */
157 I915_FENCE_FLAG_SUBMIT_PARALLEL,
158
159 /*
160 * I915_FENCE_FLAG_SKIP_PARALLEL - request with a context in a
161 * parent-child relationship (parallel submission, multi-lrc) that
162 * hit an error while generating requests in the execbuf IOCTL.
163 * Indicates this request should be skipped as another request in
164 * submission / relationship encoutered an error.
165 */
166 I915_FENCE_FLAG_SKIP_PARALLEL,
167
168 /*
169 * I915_FENCE_FLAG_COMPOSITE - Indicates fence is part of a composite
170 * fence (dma_fence_array) and i915 generated for parallel submission.
171 */
172 I915_FENCE_FLAG_COMPOSITE,
173};
174
175/*
176 * Request queue structure.
177 *
178 * The request queue allows us to note sequence numbers that have been emitted
179 * and may be associated with active buffers to be retired.
180 *
181 * By keeping this list, we can avoid having to do questionable sequence
182 * number comparisons on buffer last_read|write_seqno. It also allows an
183 * emission time to be associated with the request for tracking how far ahead
184 * of the GPU the submission is.
185 *
186 * When modifying this structure be very aware that we perform a lockless
187 * RCU lookup of it that may race against reallocation of the struct
188 * from the slab freelist. We intentionally do not zero the structure on
189 * allocation so that the lookup can use the dangling pointers (and is
190 * cogniscent that those pointers may be wrong). Instead, everything that
191 * needs to be initialised must be done so explicitly.
192 *
193 * The requests are reference counted.
194 */
195struct i915_request {
196 struct dma_fence fence;
197 spinlock_t lock;
198
199 struct drm_i915_private *i915;
200
201 /*
202 * Context and ring buffer related to this request
203 * Contexts are refcounted, so when this request is associated with a
204 * context, we must increment the context's refcount, to guarantee that
205 * it persists while any request is linked to it. Requests themselves
206 * are also refcounted, so the request will only be freed when the last
207 * reference to it is dismissed, and the code in
208 * i915_request_free() will then decrement the refcount on the
209 * context.
210 */
211 struct intel_engine_cs *engine;
212 struct intel_context *context;
213 struct intel_ring *ring;
214 struct intel_timeline __rcu *timeline;
215
216 struct list_head signal_link;
217 struct llist_node signal_node;
218
219 /*
220 * The rcu epoch of when this request was allocated. Used to judiciously
221 * apply backpressure on future allocations to ensure that under
222 * mempressure there is sufficient RCU ticks for us to reclaim our
223 * RCU protected slabs.
224 */
225 unsigned long rcustate;
226
227 /*
228 * We pin the timeline->mutex while constructing the request to
229 * ensure that no caller accidentally drops it during construction.
230 * The timeline->mutex must be held to ensure that only this caller
231 * can use the ring and manipulate the associated timeline during
232 * construction.
233 */
234 struct pin_cookie cookie;
235
236 /*
237 * Fences for the various phases in the request's lifetime.
238 *
239 * The submit fence is used to await upon all of the request's
240 * dependencies. When it is signaled, the request is ready to run.
241 * It is used by the driver to then queue the request for execution.
242 */
243 struct i915_sw_fence submit;
244 union {
245 wait_queue_entry_t submitq;
246 struct i915_sw_dma_fence_cb dmaq;
247 struct i915_request_duration_cb {
248 struct dma_fence_cb cb;
249 ktime_t emitted;
250 } duration;
251 };
252 struct llist_head execute_cb;
253 struct i915_sw_fence semaphore;
254 /*
255 * complete submit fence from an IRQ if needed for locking hierarchy
256 * reasons.
257 */
258 struct irq_work submit_work;
259
260 /*
261 * A list of everyone we wait upon, and everyone who waits upon us.
262 * Even though we will not be submitted to the hardware before the
263 * submit fence is signaled (it waits for all external events as well
264 * as our own requests), the scheduler still needs to know the
265 * dependency tree for the lifetime of the request (from execbuf
266 * to retirement), i.e. bidirectional dependency information for the
267 * request not tied to individual fences.
268 */
269 struct i915_sched_node sched;
270 struct i915_dependency dep;
271 intel_engine_mask_t execution_mask;
272
273 /*
274 * A convenience pointer to the current breadcrumb value stored in
275 * the HW status page (or our timeline's local equivalent). The full
276 * path would be rq->hw_context->ring->timeline->hwsp_seqno.
277 */
278 const u32 *hwsp_seqno;
279
280 /* Position in the ring of the start of the request */
281 u32 head;
282
283 /* Position in the ring of the start of the user packets */
284 u32 infix;
285
286 /*
287 * Position in the ring of the start of the postfix.
288 * This is required to calculate the maximum available ring space
289 * without overwriting the postfix.
290 */
291 u32 postfix;
292
293 /* Position in the ring of the end of the whole request */
294 u32 tail;
295
296 /* Position in the ring of the end of any workarounds after the tail */
297 u32 wa_tail;
298
299 /* Preallocate space in the ring for the emitting the request */
300 u32 reserved_space;
301
302 /* Batch buffer pointer for selftest internal use. */
303 I915_SELFTEST_DECLARE(struct i915_vma *batch);
304
305 struct i915_vma_resource *batch_res;
306
307#if IS_ENABLED(CONFIG_DRM_I915_CAPTURE_ERROR)
308 /*
309 * Additional buffers requested by userspace to be captured upon
310 * a GPU hang. The vma/obj on this list are protected by their
311 * active reference - all objects on this list must also be
312 * on the active_list (of their final request).
313 */
314 struct i915_capture_list *capture_list;
315#endif
316
317 /* Time at which this request was emitted, in jiffies. */
318 unsigned long emitted_jiffies;
319
320 /* timeline->request entry for this request */
321 struct list_head link;
322
323 /* Watchdog support fields. */
324 struct i915_request_watchdog {
325 struct llist_node link;
326 struct hrtimer timer;
327 } watchdog;
328
329 /*
330 * Requests may need to be stalled when using GuC submission waiting for
331 * certain GuC operations to complete. If that is the case, stalled
332 * requests are added to a per context list of stalled requests. The
333 * below list_head is the link in that list. Protected by
334 * ce->guc_state.lock.
335 */
336 struct list_head guc_fence_link;
337
338 /*
339 * Priority level while the request is in flight. Differs
340 * from i915 scheduler priority. See comment above
341 * I915_SCHEDULER_CAP_STATIC_PRIORITY_MAP for details. Protected by
342 * ce->guc_active.lock. Two special values (GUC_PRIO_INIT and
343 * GUC_PRIO_FINI) outside the GuC priority range are used to indicate
344 * if the priority has not been initialized yet or if no more updates
345 * are possible because the request has completed.
346 */
347#define GUC_PRIO_INIT 0xff
348#define GUC_PRIO_FINI 0xfe
349 u8 guc_prio;
350
351 /*
352 * wait queue entry used to wait on the HuC load to complete
353 */
354 wait_queue_entry_t hucq;
355
356 I915_SELFTEST_DECLARE(struct {
357 struct list_head link;
358 unsigned long delay;
359 } mock;)
360};
361
362#define I915_FENCE_GFP (GFP_KERNEL | __GFP_RETRY_MAYFAIL | __GFP_NOWARN)
363
364extern const struct dma_fence_ops i915_fence_ops;
365
366static inline bool dma_fence_is_i915(const struct dma_fence *fence)
367{
368 return fence->ops == &i915_fence_ops;
369}
370
371struct kmem_cache *i915_request_slab_cache(void);
372
373struct i915_request * __must_check
374__i915_request_create(struct intel_context *ce, gfp_t gfp);
375struct i915_request * __must_check
376i915_request_create(struct intel_context *ce);
377
378void __i915_request_skip(struct i915_request *rq);
379bool i915_request_set_error_once(struct i915_request *rq, int error);
380struct i915_request *i915_request_mark_eio(struct i915_request *rq);
381
382struct i915_request *__i915_request_commit(struct i915_request *request);
383void __i915_request_queue(struct i915_request *rq,
384 const struct i915_sched_attr *attr);
385void __i915_request_queue_bh(struct i915_request *rq);
386
387bool i915_request_retire(struct i915_request *rq);
388void i915_request_retire_upto(struct i915_request *rq);
389
390static inline struct i915_request *
391to_request(struct dma_fence *fence)
392{
393 /* We assume that NULL fence/request are interoperable */
394 BUILD_BUG_ON(offsetof(struct i915_request, fence) != 0);
395 GEM_BUG_ON(fence && !dma_fence_is_i915(fence));
396 return container_of(fence, struct i915_request, fence);
397}
398
399static inline struct i915_request *
400i915_request_get(struct i915_request *rq)
401{
402 return to_request(dma_fence_get(&rq->fence));
403}
404
405static inline struct i915_request *
406i915_request_get_rcu(struct i915_request *rq)
407{
408 return to_request(dma_fence_get_rcu(&rq->fence));
409}
410
411static inline void
412i915_request_put(struct i915_request *rq)
413{
414 dma_fence_put(&rq->fence);
415}
416
417int i915_request_await_object(struct i915_request *to,
418 struct drm_i915_gem_object *obj,
419 bool write);
420int i915_request_await_dma_fence(struct i915_request *rq,
421 struct dma_fence *fence);
422int i915_request_await_deps(struct i915_request *rq, const struct i915_deps *deps);
423int i915_request_await_execution(struct i915_request *rq,
424 struct dma_fence *fence);
425
426void i915_request_add(struct i915_request *rq);
427
428bool __i915_request_submit(struct i915_request *request);
429void i915_request_submit(struct i915_request *request);
430
431void __i915_request_unsubmit(struct i915_request *request);
432void i915_request_unsubmit(struct i915_request *request);
433
434void i915_request_cancel(struct i915_request *rq, int error);
435
436long i915_request_wait_timeout(struct i915_request *rq,
437 unsigned int flags,
438 long timeout)
439 __attribute__((nonnull(1)));
440
441long i915_request_wait(struct i915_request *rq,
442 unsigned int flags,
443 long timeout)
444 __attribute__((nonnull(1)));
445#define I915_WAIT_INTERRUPTIBLE BIT(0)
446#define I915_WAIT_PRIORITY BIT(1) /* small priority bump for the request */
447#define I915_WAIT_ALL BIT(2) /* used by i915_gem_object_wait() */
448
449void i915_request_show(struct drm_printer *m,
450 const struct i915_request *rq,
451 const char *prefix,
452 int indent);
453
454static inline bool i915_request_signaled(const struct i915_request *rq)
455{
456 /* The request may live longer than its HWSP, so check flags first! */
457 return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &rq->fence.flags);
458}
459
460static inline bool i915_request_is_active(const struct i915_request *rq)
461{
462 return test_bit(I915_FENCE_FLAG_ACTIVE, &rq->fence.flags);
463}
464
465static inline bool i915_request_in_priority_queue(const struct i915_request *rq)
466{
467 return test_bit(I915_FENCE_FLAG_PQUEUE, &rq->fence.flags);
468}
469
470static inline bool
471i915_request_has_initial_breadcrumb(const struct i915_request *rq)
472{
473 return test_bit(I915_FENCE_FLAG_INITIAL_BREADCRUMB, &rq->fence.flags);
474}
475
476/*
477 * Returns true if seq1 is later than seq2.
478 */
479static inline bool i915_seqno_passed(u32 seq1, u32 seq2)
480{
481 return (s32)(seq1 - seq2) >= 0;
482}
483
484static inline u32 __hwsp_seqno(const struct i915_request *rq)
485{
486 const u32 *hwsp = READ_ONCE(rq->hwsp_seqno);
487
488 return READ_ONCE(*hwsp);
489}
490
491/**
492 * hwsp_seqno - the current breadcrumb value in the HW status page
493 * @rq: the request, to chase the relevant HW status page
494 *
495 * The emphasis in naming here is that hwsp_seqno() is not a property of the
496 * request, but an indication of the current HW state (associated with this
497 * request). Its value will change as the GPU executes more requests.
498 *
499 * Returns the current breadcrumb value in the associated HW status page (or
500 * the local timeline's equivalent) for this request. The request itself
501 * has the associated breadcrumb value of rq->fence.seqno, when the HW
502 * status page has that breadcrumb or later, this request is complete.
503 */
504static inline u32 hwsp_seqno(const struct i915_request *rq)
505{
506 u32 seqno;
507
508 rcu_read_lock(); /* the HWSP may be freed at runtime */
509 seqno = __hwsp_seqno(rq);
510 rcu_read_unlock();
511
512 return seqno;
513}
514
515static inline bool __i915_request_has_started(const struct i915_request *rq)
516{
517 return i915_seqno_passed(__hwsp_seqno(rq), rq->fence.seqno - 1);
518}
519
520/**
521 * i915_request_started - check if the request has begun being executed
522 * @rq: the request
523 *
524 * If the timeline is not using initial breadcrumbs, a request is
525 * considered started if the previous request on its timeline (i.e.
526 * context) has been signaled.
527 *
528 * If the timeline is using semaphores, it will also be emitting an
529 * "initial breadcrumb" after the semaphores are complete and just before
530 * it began executing the user payload. A request can therefore be active
531 * on the HW and not yet started as it is still busywaiting on its
532 * dependencies (via HW semaphores).
533 *
534 * If the request has started, its dependencies will have been signaled
535 * (either by fences or by semaphores) and it will have begun processing
536 * the user payload.
537 *
538 * However, even if a request has started, it may have been preempted and
539 * so no longer active, or it may have already completed.
540 *
541 * See also i915_request_is_active().
542 *
543 * Returns true if the request has begun executing the user payload, or
544 * has completed:
545 */
546static inline bool i915_request_started(const struct i915_request *rq)
547{
548 bool result;
549
550 if (i915_request_signaled(rq))
551 return true;
552
553 result = true;
554 rcu_read_lock(); /* the HWSP may be freed at runtime */
555 if (likely(!i915_request_signaled(rq)))
556 /* Remember: started but may have since been preempted! */
557 result = __i915_request_has_started(rq);
558 rcu_read_unlock();
559
560 return result;
561}
562
563/**
564 * i915_request_is_running - check if the request may actually be executing
565 * @rq: the request
566 *
567 * Returns true if the request is currently submitted to hardware, has passed
568 * its start point (i.e. the context is setup and not busywaiting). Note that
569 * it may no longer be running by the time the function returns!
570 */
571static inline bool i915_request_is_running(const struct i915_request *rq)
572{
573 bool result;
574
575 if (!i915_request_is_active(rq))
576 return false;
577
578 rcu_read_lock();
579 result = __i915_request_has_started(rq) && i915_request_is_active(rq);
580 rcu_read_unlock();
581
582 return result;
583}
584
585/**
586 * i915_request_is_ready - check if the request is ready for execution
587 * @rq: the request
588 *
589 * Upon construction, the request is instructed to wait upon various
590 * signals before it is ready to be executed by the HW. That is, we do
591 * not want to start execution and read data before it is written. In practice,
592 * this is controlled with a mixture of interrupts and semaphores. Once
593 * the submit fence is completed, the backend scheduler will place the
594 * request into its queue and from there submit it for execution. So we
595 * can detect when a request is eligible for execution (and is under control
596 * of the scheduler) by querying where it is in any of the scheduler's lists.
597 *
598 * Returns true if the request is ready for execution (it may be inflight),
599 * false otherwise.
600 */
601static inline bool i915_request_is_ready(const struct i915_request *rq)
602{
603 return !list_empty(&rq->sched.link);
604}
605
606static inline bool __i915_request_is_complete(const struct i915_request *rq)
607{
608 return i915_seqno_passed(__hwsp_seqno(rq), rq->fence.seqno);
609}
610
611static inline bool i915_request_completed(const struct i915_request *rq)
612{
613 bool result;
614
615 if (i915_request_signaled(rq))
616 return true;
617
618 result = true;
619 rcu_read_lock(); /* the HWSP may be freed at runtime */
620 if (likely(!i915_request_signaled(rq)))
621 result = __i915_request_is_complete(rq);
622 rcu_read_unlock();
623
624 return result;
625}
626
627static inline void i915_request_mark_complete(struct i915_request *rq)
628{
629 WRITE_ONCE(rq->hwsp_seqno, /* decouple from HWSP */
630 (u32 *)&rq->fence.seqno);
631}
632
633static inline bool i915_request_has_waitboost(const struct i915_request *rq)
634{
635 return test_bit(I915_FENCE_FLAG_BOOST, &rq->fence.flags);
636}
637
638static inline bool i915_request_has_nopreempt(const struct i915_request *rq)
639{
640 /* Preemption should only be disabled very rarely */
641 return unlikely(test_bit(I915_FENCE_FLAG_NOPREEMPT, &rq->fence.flags));
642}
643
644static inline bool i915_request_has_sentinel(const struct i915_request *rq)
645{
646 return unlikely(test_bit(I915_FENCE_FLAG_SENTINEL, &rq->fence.flags));
647}
648
649static inline bool i915_request_on_hold(const struct i915_request *rq)
650{
651 return unlikely(test_bit(I915_FENCE_FLAG_HOLD, &rq->fence.flags));
652}
653
654static inline void i915_request_set_hold(struct i915_request *rq)
655{
656 set_bit(I915_FENCE_FLAG_HOLD, &rq->fence.flags);
657}
658
659static inline void i915_request_clear_hold(struct i915_request *rq)
660{
661 clear_bit(I915_FENCE_FLAG_HOLD, &rq->fence.flags);
662}
663
664static inline struct intel_timeline *
665i915_request_timeline(const struct i915_request *rq)
666{
667 /* Valid only while the request is being constructed (or retired). */
668 return rcu_dereference_protected(rq->timeline,
669 lockdep_is_held(&rcu_access_pointer(rq->timeline)->mutex) ||
670 test_bit(CONTEXT_IS_PARKING, &rq->context->flags));
671}
672
673static inline struct i915_gem_context *
674i915_request_gem_context(const struct i915_request *rq)
675{
676 /* Valid only while the request is being constructed (or retired). */
677 return rcu_dereference_protected(rq->context->gem_context, true);
678}
679
680static inline struct intel_timeline *
681i915_request_active_timeline(const struct i915_request *rq)
682{
683 /*
684 * When in use during submission, we are protected by a guarantee that
685 * the context/timeline is pinned and must remain pinned until after
686 * this submission.
687 */
688 return rcu_dereference_protected(rq->timeline,
689 lockdep_is_held(&rq->engine->sched_engine->lock));
690}
691
692static inline u32
693i915_request_active_seqno(const struct i915_request *rq)
694{
695 u32 hwsp_phys_base =
696 page_mask_bits(i915_request_active_timeline(rq)->hwsp_offset);
697 u32 hwsp_relative_offset = offset_in_page(rq->hwsp_seqno);
698
699 /*
700 * Because of wraparound, we cannot simply take tl->hwsp_offset,
701 * but instead use the fact that the relative for vaddr is the
702 * offset as for hwsp_offset. Take the top bits from tl->hwsp_offset
703 * and combine them with the relative offset in rq->hwsp_seqno.
704 *
705 * As rw->hwsp_seqno is rewritten when signaled, this only works
706 * when the request isn't signaled yet, but at that point you
707 * no longer need the offset.
708 */
709
710 return hwsp_phys_base + hwsp_relative_offset;
711}
712
713bool
714i915_request_active_engine(struct i915_request *rq,
715 struct intel_engine_cs **active);
716
717void i915_request_notify_execute_cb_imm(struct i915_request *rq);
718
719enum i915_request_state {
720 I915_REQUEST_UNKNOWN = 0,
721 I915_REQUEST_COMPLETE,
722 I915_REQUEST_PENDING,
723 I915_REQUEST_QUEUED,
724 I915_REQUEST_ACTIVE,
725};
726
727enum i915_request_state i915_test_request_state(struct i915_request *rq);
728
729void i915_request_module_exit(void);
730int i915_request_module_init(void);
731
732#endif /* I915_REQUEST_H */
1/*
2 * Copyright © 2008-2018 Intel Corporation
3 *
4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
6 * to deal in the Software without restriction, including without limitation
7 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 * and/or sell copies of the Software, and to permit persons to whom the
9 * Software is furnished to do so, subject to the following conditions:
10 *
11 * The above copyright notice and this permission notice (including the next
12 * paragraph) shall be included in all copies or substantial portions of the
13 * Software.
14 *
15 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
18 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
20 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
21 * IN THE SOFTWARE.
22 *
23 */
24
25#ifndef I915_REQUEST_H
26#define I915_REQUEST_H
27
28#include <linux/dma-fence.h>
29
30#include "i915_gem.h"
31#include "i915_sw_fence.h"
32
33#include <uapi/drm/i915_drm.h>
34
35struct drm_file;
36struct drm_i915_gem_object;
37struct i915_request;
38
39struct intel_wait {
40 struct rb_node node;
41 struct task_struct *tsk;
42 struct i915_request *request;
43 u32 seqno;
44};
45
46struct intel_signal_node {
47 struct intel_wait wait;
48 struct list_head link;
49};
50
51struct i915_dependency {
52 struct i915_priotree *signaler;
53 struct list_head signal_link;
54 struct list_head wait_link;
55 struct list_head dfs_link;
56 unsigned long flags;
57#define I915_DEPENDENCY_ALLOC BIT(0)
58};
59
60/*
61 * "People assume that time is a strict progression of cause to effect, but
62 * actually, from a nonlinear, non-subjective viewpoint, it's more like a big
63 * ball of wibbly-wobbly, timey-wimey ... stuff." -The Doctor, 2015
64 *
65 * Requests exist in a complex web of interdependencies. Each request
66 * has to wait for some other request to complete before it is ready to be run
67 * (e.g. we have to wait until the pixels have been rendering into a texture
68 * before we can copy from it). We track the readiness of a request in terms
69 * of fences, but we also need to keep the dependency tree for the lifetime
70 * of the request (beyond the life of an individual fence). We use the tree
71 * at various points to reorder the requests whilst keeping the requests
72 * in order with respect to their various dependencies.
73 */
74struct i915_priotree {
75 struct list_head signalers_list; /* those before us, we depend upon */
76 struct list_head waiters_list; /* those after us, they depend upon us */
77 struct list_head link;
78 int priority;
79};
80
81enum {
82 I915_PRIORITY_MIN = I915_CONTEXT_MIN_USER_PRIORITY - 1,
83 I915_PRIORITY_NORMAL = I915_CONTEXT_DEFAULT_PRIORITY,
84 I915_PRIORITY_MAX = I915_CONTEXT_MAX_USER_PRIORITY + 1,
85
86 I915_PRIORITY_INVALID = INT_MIN
87};
88
89struct i915_capture_list {
90 struct i915_capture_list *next;
91 struct i915_vma *vma;
92};
93
94/**
95 * Request queue structure.
96 *
97 * The request queue allows us to note sequence numbers that have been emitted
98 * and may be associated with active buffers to be retired.
99 *
100 * By keeping this list, we can avoid having to do questionable sequence
101 * number comparisons on buffer last_read|write_seqno. It also allows an
102 * emission time to be associated with the request for tracking how far ahead
103 * of the GPU the submission is.
104 *
105 * When modifying this structure be very aware that we perform a lockless
106 * RCU lookup of it that may race against reallocation of the struct
107 * from the slab freelist. We intentionally do not zero the structure on
108 * allocation so that the lookup can use the dangling pointers (and is
109 * cogniscent that those pointers may be wrong). Instead, everything that
110 * needs to be initialised must be done so explicitly.
111 *
112 * The requests are reference counted.
113 */
114struct i915_request {
115 struct dma_fence fence;
116 spinlock_t lock;
117
118 /** On Which ring this request was generated */
119 struct drm_i915_private *i915;
120
121 /**
122 * Context and ring buffer related to this request
123 * Contexts are refcounted, so when this request is associated with a
124 * context, we must increment the context's refcount, to guarantee that
125 * it persists while any request is linked to it. Requests themselves
126 * are also refcounted, so the request will only be freed when the last
127 * reference to it is dismissed, and the code in
128 * i915_request_free() will then decrement the refcount on the
129 * context.
130 */
131 struct i915_gem_context *ctx;
132 struct intel_engine_cs *engine;
133 struct intel_ring *ring;
134 struct intel_timeline *timeline;
135 struct intel_signal_node signaling;
136
137 /*
138 * Fences for the various phases in the request's lifetime.
139 *
140 * The submit fence is used to await upon all of the request's
141 * dependencies. When it is signaled, the request is ready to run.
142 * It is used by the driver to then queue the request for execution.
143 */
144 struct i915_sw_fence submit;
145 wait_queue_entry_t submitq;
146 wait_queue_head_t execute;
147
148 /*
149 * A list of everyone we wait upon, and everyone who waits upon us.
150 * Even though we will not be submitted to the hardware before the
151 * submit fence is signaled (it waits for all external events as well
152 * as our own requests), the scheduler still needs to know the
153 * dependency tree for the lifetime of the request (from execbuf
154 * to retirement), i.e. bidirectional dependency information for the
155 * request not tied to individual fences.
156 */
157 struct i915_priotree priotree;
158 struct i915_dependency dep;
159
160 /**
161 * GEM sequence number associated with this request on the
162 * global execution timeline. It is zero when the request is not
163 * on the HW queue (i.e. not on the engine timeline list).
164 * Its value is guarded by the timeline spinlock.
165 */
166 u32 global_seqno;
167
168 /** Position in the ring of the start of the request */
169 u32 head;
170
171 /**
172 * Position in the ring of the start of the postfix.
173 * This is required to calculate the maximum available ring space
174 * without overwriting the postfix.
175 */
176 u32 postfix;
177
178 /** Position in the ring of the end of the whole request */
179 u32 tail;
180
181 /** Position in the ring of the end of any workarounds after the tail */
182 u32 wa_tail;
183
184 /** Preallocate space in the ring for the emitting the request */
185 u32 reserved_space;
186
187 /** Batch buffer related to this request if any (used for
188 * error state dump only).
189 */
190 struct i915_vma *batch;
191 /**
192 * Additional buffers requested by userspace to be captured upon
193 * a GPU hang. The vma/obj on this list are protected by their
194 * active reference - all objects on this list must also be
195 * on the active_list (of their final request).
196 */
197 struct i915_capture_list *capture_list;
198 struct list_head active_list;
199
200 /** Time at which this request was emitted, in jiffies. */
201 unsigned long emitted_jiffies;
202
203 bool waitboost;
204
205 /** engine->request_list entry for this request */
206 struct list_head link;
207
208 /** ring->request_list entry for this request */
209 struct list_head ring_link;
210
211 struct drm_i915_file_private *file_priv;
212 /** file_priv list entry for this request */
213 struct list_head client_link;
214};
215
216#define I915_FENCE_GFP (GFP_KERNEL | __GFP_RETRY_MAYFAIL | __GFP_NOWARN)
217
218extern const struct dma_fence_ops i915_fence_ops;
219
220static inline bool dma_fence_is_i915(const struct dma_fence *fence)
221{
222 return fence->ops == &i915_fence_ops;
223}
224
225struct i915_request * __must_check
226i915_request_alloc(struct intel_engine_cs *engine,
227 struct i915_gem_context *ctx);
228void i915_request_retire_upto(struct i915_request *rq);
229
230static inline struct i915_request *
231to_request(struct dma_fence *fence)
232{
233 /* We assume that NULL fence/request are interoperable */
234 BUILD_BUG_ON(offsetof(struct i915_request, fence) != 0);
235 GEM_BUG_ON(fence && !dma_fence_is_i915(fence));
236 return container_of(fence, struct i915_request, fence);
237}
238
239static inline struct i915_request *
240i915_request_get(struct i915_request *rq)
241{
242 return to_request(dma_fence_get(&rq->fence));
243}
244
245static inline struct i915_request *
246i915_request_get_rcu(struct i915_request *rq)
247{
248 return to_request(dma_fence_get_rcu(&rq->fence));
249}
250
251static inline void
252i915_request_put(struct i915_request *rq)
253{
254 dma_fence_put(&rq->fence);
255}
256
257/**
258 * i915_request_global_seqno - report the current global seqno
259 * @request - the request
260 *
261 * A request is assigned a global seqno only when it is on the hardware
262 * execution queue. The global seqno can be used to maintain a list of
263 * requests on the same engine in retirement order, for example for
264 * constructing a priority queue for waiting. Prior to its execution, or
265 * if it is subsequently removed in the event of preemption, its global
266 * seqno is zero. As both insertion and removal from the execution queue
267 * may operate in IRQ context, it is not guarded by the usual struct_mutex
268 * BKL. Instead those relying on the global seqno must be prepared for its
269 * value to change between reads. Only when the request is complete can
270 * the global seqno be stable (due to the memory barriers on submitting
271 * the commands to the hardware to write the breadcrumb, if the HWS shows
272 * that it has passed the global seqno and the global seqno is unchanged
273 * after the read, it is indeed complete).
274 */
275static u32
276i915_request_global_seqno(const struct i915_request *request)
277{
278 return READ_ONCE(request->global_seqno);
279}
280
281int i915_request_await_object(struct i915_request *to,
282 struct drm_i915_gem_object *obj,
283 bool write);
284int i915_request_await_dma_fence(struct i915_request *rq,
285 struct dma_fence *fence);
286
287void __i915_request_add(struct i915_request *rq, bool flush_caches);
288#define i915_request_add(rq) \
289 __i915_request_add(rq, false)
290
291void __i915_request_submit(struct i915_request *request);
292void i915_request_submit(struct i915_request *request);
293
294void __i915_request_unsubmit(struct i915_request *request);
295void i915_request_unsubmit(struct i915_request *request);
296
297long i915_request_wait(struct i915_request *rq,
298 unsigned int flags,
299 long timeout)
300 __attribute__((nonnull(1)));
301#define I915_WAIT_INTERRUPTIBLE BIT(0)
302#define I915_WAIT_LOCKED BIT(1) /* struct_mutex held, handle GPU reset */
303#define I915_WAIT_ALL BIT(2) /* used by i915_gem_object_wait() */
304
305static inline u32 intel_engine_get_seqno(struct intel_engine_cs *engine);
306
307/**
308 * Returns true if seq1 is later than seq2.
309 */
310static inline bool i915_seqno_passed(u32 seq1, u32 seq2)
311{
312 return (s32)(seq1 - seq2) >= 0;
313}
314
315static inline bool
316__i915_request_completed(const struct i915_request *rq, u32 seqno)
317{
318 GEM_BUG_ON(!seqno);
319 return i915_seqno_passed(intel_engine_get_seqno(rq->engine), seqno) &&
320 seqno == i915_request_global_seqno(rq);
321}
322
323static inline bool i915_request_completed(const struct i915_request *rq)
324{
325 u32 seqno;
326
327 seqno = i915_request_global_seqno(rq);
328 if (!seqno)
329 return false;
330
331 return __i915_request_completed(rq, seqno);
332}
333
334static inline bool i915_request_started(const struct i915_request *rq)
335{
336 u32 seqno;
337
338 seqno = i915_request_global_seqno(rq);
339 if (!seqno)
340 return false;
341
342 return i915_seqno_passed(intel_engine_get_seqno(rq->engine),
343 seqno - 1);
344}
345
346static inline bool i915_priotree_signaled(const struct i915_priotree *pt)
347{
348 const struct i915_request *rq =
349 container_of(pt, const struct i915_request, priotree);
350
351 return i915_request_completed(rq);
352}
353
354void i915_retire_requests(struct drm_i915_private *i915);
355
356/*
357 * We treat requests as fences. This is not be to confused with our
358 * "fence registers" but pipeline synchronisation objects ala GL_ARB_sync.
359 * We use the fences to synchronize access from the CPU with activity on the
360 * GPU, for example, we should not rewrite an object's PTE whilst the GPU
361 * is reading them. We also track fences at a higher level to provide
362 * implicit synchronisation around GEM objects, e.g. set-domain will wait
363 * for outstanding GPU rendering before marking the object ready for CPU
364 * access, or a pageflip will wait until the GPU is complete before showing
365 * the frame on the scanout.
366 *
367 * In order to use a fence, the object must track the fence it needs to
368 * serialise with. For example, GEM objects want to track both read and
369 * write access so that we can perform concurrent read operations between
370 * the CPU and GPU engines, as well as waiting for all rendering to
371 * complete, or waiting for the last GPU user of a "fence register". The
372 * object then embeds a #i915_gem_active to track the most recent (in
373 * retirement order) request relevant for the desired mode of access.
374 * The #i915_gem_active is updated with i915_gem_active_set() to track the
375 * most recent fence request, typically this is done as part of
376 * i915_vma_move_to_active().
377 *
378 * When the #i915_gem_active completes (is retired), it will
379 * signal its completion to the owner through a callback as well as mark
380 * itself as idle (i915_gem_active.request == NULL). The owner
381 * can then perform any action, such as delayed freeing of an active
382 * resource including itself.
383 */
384struct i915_gem_active;
385
386typedef void (*i915_gem_retire_fn)(struct i915_gem_active *,
387 struct i915_request *);
388
389struct i915_gem_active {
390 struct i915_request __rcu *request;
391 struct list_head link;
392 i915_gem_retire_fn retire;
393};
394
395void i915_gem_retire_noop(struct i915_gem_active *,
396 struct i915_request *request);
397
398/**
399 * init_request_active - prepares the activity tracker for use
400 * @active - the active tracker
401 * @func - a callback when then the tracker is retired (becomes idle),
402 * can be NULL
403 *
404 * init_request_active() prepares the embedded @active struct for use as
405 * an activity tracker, that is for tracking the last known active request
406 * associated with it. When the last request becomes idle, when it is retired
407 * after completion, the optional callback @func is invoked.
408 */
409static inline void
410init_request_active(struct i915_gem_active *active,
411 i915_gem_retire_fn retire)
412{
413 INIT_LIST_HEAD(&active->link);
414 active->retire = retire ?: i915_gem_retire_noop;
415}
416
417/**
418 * i915_gem_active_set - updates the tracker to watch the current request
419 * @active - the active tracker
420 * @request - the request to watch
421 *
422 * i915_gem_active_set() watches the given @request for completion. Whilst
423 * that @request is busy, the @active reports busy. When that @request is
424 * retired, the @active tracker is updated to report idle.
425 */
426static inline void
427i915_gem_active_set(struct i915_gem_active *active,
428 struct i915_request *request)
429{
430 list_move(&active->link, &request->active_list);
431 rcu_assign_pointer(active->request, request);
432}
433
434/**
435 * i915_gem_active_set_retire_fn - updates the retirement callback
436 * @active - the active tracker
437 * @fn - the routine called when the request is retired
438 * @mutex - struct_mutex used to guard retirements
439 *
440 * i915_gem_active_set_retire_fn() updates the function pointer that
441 * is called when the final request associated with the @active tracker
442 * is retired.
443 */
444static inline void
445i915_gem_active_set_retire_fn(struct i915_gem_active *active,
446 i915_gem_retire_fn fn,
447 struct mutex *mutex)
448{
449 lockdep_assert_held(mutex);
450 active->retire = fn ?: i915_gem_retire_noop;
451}
452
453static inline struct i915_request *
454__i915_gem_active_peek(const struct i915_gem_active *active)
455{
456 /*
457 * Inside the error capture (running with the driver in an unknown
458 * state), we want to bend the rules slightly (a lot).
459 *
460 * Work is in progress to make it safer, in the meantime this keeps
461 * the known issue from spamming the logs.
462 */
463 return rcu_dereference_protected(active->request, 1);
464}
465
466/**
467 * i915_gem_active_raw - return the active request
468 * @active - the active tracker
469 *
470 * i915_gem_active_raw() returns the current request being tracked, or NULL.
471 * It does not obtain a reference on the request for the caller, so the caller
472 * must hold struct_mutex.
473 */
474static inline struct i915_request *
475i915_gem_active_raw(const struct i915_gem_active *active, struct mutex *mutex)
476{
477 return rcu_dereference_protected(active->request,
478 lockdep_is_held(mutex));
479}
480
481/**
482 * i915_gem_active_peek - report the active request being monitored
483 * @active - the active tracker
484 *
485 * i915_gem_active_peek() returns the current request being tracked if
486 * still active, or NULL. It does not obtain a reference on the request
487 * for the caller, so the caller must hold struct_mutex.
488 */
489static inline struct i915_request *
490i915_gem_active_peek(const struct i915_gem_active *active, struct mutex *mutex)
491{
492 struct i915_request *request;
493
494 request = i915_gem_active_raw(active, mutex);
495 if (!request || i915_request_completed(request))
496 return NULL;
497
498 return request;
499}
500
501/**
502 * i915_gem_active_get - return a reference to the active request
503 * @active - the active tracker
504 *
505 * i915_gem_active_get() returns a reference to the active request, or NULL
506 * if the active tracker is idle. The caller must hold struct_mutex.
507 */
508static inline struct i915_request *
509i915_gem_active_get(const struct i915_gem_active *active, struct mutex *mutex)
510{
511 return i915_request_get(i915_gem_active_peek(active, mutex));
512}
513
514/**
515 * __i915_gem_active_get_rcu - return a reference to the active request
516 * @active - the active tracker
517 *
518 * __i915_gem_active_get() returns a reference to the active request, or NULL
519 * if the active tracker is idle. The caller must hold the RCU read lock, but
520 * the returned pointer is safe to use outside of RCU.
521 */
522static inline struct i915_request *
523__i915_gem_active_get_rcu(const struct i915_gem_active *active)
524{
525 /*
526 * Performing a lockless retrieval of the active request is super
527 * tricky. SLAB_TYPESAFE_BY_RCU merely guarantees that the backing
528 * slab of request objects will not be freed whilst we hold the
529 * RCU read lock. It does not guarantee that the request itself
530 * will not be freed and then *reused*. Viz,
531 *
532 * Thread A Thread B
533 *
534 * rq = active.request
535 * retire(rq) -> free(rq);
536 * (rq is now first on the slab freelist)
537 * active.request = NULL
538 *
539 * rq = new submission on a new object
540 * ref(rq)
541 *
542 * To prevent the request from being reused whilst the caller
543 * uses it, we take a reference like normal. Whilst acquiring
544 * the reference we check that it is not in a destroyed state
545 * (refcnt == 0). That prevents the request being reallocated
546 * whilst the caller holds on to it. To check that the request
547 * was not reallocated as we acquired the reference we have to
548 * check that our request remains the active request across
549 * the lookup, in the same manner as a seqlock. The visibility
550 * of the pointer versus the reference counting is controlled
551 * by using RCU barriers (rcu_dereference and rcu_assign_pointer).
552 *
553 * In the middle of all that, we inspect whether the request is
554 * complete. Retiring is lazy so the request may be completed long
555 * before the active tracker is updated. Querying whether the
556 * request is complete is far cheaper (as it involves no locked
557 * instructions setting cachelines to exclusive) than acquiring
558 * the reference, so we do it first. The RCU read lock ensures the
559 * pointer dereference is valid, but does not ensure that the
560 * seqno nor HWS is the right one! However, if the request was
561 * reallocated, that means the active tracker's request was complete.
562 * If the new request is also complete, then both are and we can
563 * just report the active tracker is idle. If the new request is
564 * incomplete, then we acquire a reference on it and check that
565 * it remained the active request.
566 *
567 * It is then imperative that we do not zero the request on
568 * reallocation, so that we can chase the dangling pointers!
569 * See i915_request_alloc().
570 */
571 do {
572 struct i915_request *request;
573
574 request = rcu_dereference(active->request);
575 if (!request || i915_request_completed(request))
576 return NULL;
577
578 /*
579 * An especially silly compiler could decide to recompute the
580 * result of i915_request_completed, more specifically
581 * re-emit the load for request->fence.seqno. A race would catch
582 * a later seqno value, which could flip the result from true to
583 * false. Which means part of the instructions below might not
584 * be executed, while later on instructions are executed. Due to
585 * barriers within the refcounting the inconsistency can't reach
586 * past the call to i915_request_get_rcu, but not executing
587 * that while still executing i915_request_put() creates
588 * havoc enough. Prevent this with a compiler barrier.
589 */
590 barrier();
591
592 request = i915_request_get_rcu(request);
593
594 /*
595 * What stops the following rcu_access_pointer() from occurring
596 * before the above i915_request_get_rcu()? If we were
597 * to read the value before pausing to get the reference to
598 * the request, we may not notice a change in the active
599 * tracker.
600 *
601 * The rcu_access_pointer() is a mere compiler barrier, which
602 * means both the CPU and compiler are free to perform the
603 * memory read without constraint. The compiler only has to
604 * ensure that any operations after the rcu_access_pointer()
605 * occur afterwards in program order. This means the read may
606 * be performed earlier by an out-of-order CPU, or adventurous
607 * compiler.
608 *
609 * The atomic operation at the heart of
610 * i915_request_get_rcu(), see dma_fence_get_rcu(), is
611 * atomic_inc_not_zero() which is only a full memory barrier
612 * when successful. That is, if i915_request_get_rcu()
613 * returns the request (and so with the reference counted
614 * incremented) then the following read for rcu_access_pointer()
615 * must occur after the atomic operation and so confirm
616 * that this request is the one currently being tracked.
617 *
618 * The corresponding write barrier is part of
619 * rcu_assign_pointer().
620 */
621 if (!request || request == rcu_access_pointer(active->request))
622 return rcu_pointer_handoff(request);
623
624 i915_request_put(request);
625 } while (1);
626}
627
628/**
629 * i915_gem_active_get_unlocked - return a reference to the active request
630 * @active - the active tracker
631 *
632 * i915_gem_active_get_unlocked() returns a reference to the active request,
633 * or NULL if the active tracker is idle. The reference is obtained under RCU,
634 * so no locking is required by the caller.
635 *
636 * The reference should be freed with i915_request_put().
637 */
638static inline struct i915_request *
639i915_gem_active_get_unlocked(const struct i915_gem_active *active)
640{
641 struct i915_request *request;
642
643 rcu_read_lock();
644 request = __i915_gem_active_get_rcu(active);
645 rcu_read_unlock();
646
647 return request;
648}
649
650/**
651 * i915_gem_active_isset - report whether the active tracker is assigned
652 * @active - the active tracker
653 *
654 * i915_gem_active_isset() returns true if the active tracker is currently
655 * assigned to a request. Due to the lazy retiring, that request may be idle
656 * and this may report stale information.
657 */
658static inline bool
659i915_gem_active_isset(const struct i915_gem_active *active)
660{
661 return rcu_access_pointer(active->request);
662}
663
664/**
665 * i915_gem_active_wait - waits until the request is completed
666 * @active - the active request on which to wait
667 * @flags - how to wait
668 * @timeout - how long to wait at most
669 * @rps - userspace client to charge for a waitboost
670 *
671 * i915_gem_active_wait() waits until the request is completed before
672 * returning, without requiring any locks to be held. Note that it does not
673 * retire any requests before returning.
674 *
675 * This function relies on RCU in order to acquire the reference to the active
676 * request without holding any locks. See __i915_gem_active_get_rcu() for the
677 * glory details on how that is managed. Once the reference is acquired, we
678 * can then wait upon the request, and afterwards release our reference,
679 * free of any locking.
680 *
681 * This function wraps i915_request_wait(), see it for the full details on
682 * the arguments.
683 *
684 * Returns 0 if successful, or a negative error code.
685 */
686static inline int
687i915_gem_active_wait(const struct i915_gem_active *active, unsigned int flags)
688{
689 struct i915_request *request;
690 long ret = 0;
691
692 request = i915_gem_active_get_unlocked(active);
693 if (request) {
694 ret = i915_request_wait(request, flags, MAX_SCHEDULE_TIMEOUT);
695 i915_request_put(request);
696 }
697
698 return ret < 0 ? ret : 0;
699}
700
701/**
702 * i915_gem_active_retire - waits until the request is retired
703 * @active - the active request on which to wait
704 *
705 * i915_gem_active_retire() waits until the request is completed,
706 * and then ensures that at least the retirement handler for this
707 * @active tracker is called before returning. If the @active
708 * tracker is idle, the function returns immediately.
709 */
710static inline int __must_check
711i915_gem_active_retire(struct i915_gem_active *active,
712 struct mutex *mutex)
713{
714 struct i915_request *request;
715 long ret;
716
717 request = i915_gem_active_raw(active, mutex);
718 if (!request)
719 return 0;
720
721 ret = i915_request_wait(request,
722 I915_WAIT_INTERRUPTIBLE | I915_WAIT_LOCKED,
723 MAX_SCHEDULE_TIMEOUT);
724 if (ret < 0)
725 return ret;
726
727 list_del_init(&active->link);
728 RCU_INIT_POINTER(active->request, NULL);
729
730 active->retire(active, request);
731
732 return 0;
733}
734
735#define for_each_active(mask, idx) \
736 for (; mask ? idx = ffs(mask) - 1, 1 : 0; mask &= ~BIT(idx))
737
738#endif /* I915_REQUEST_H */