drm/i915: Assert that the request is on the execution queue before being removed
authorChris Wilson <chris@chris-wilson.co.uk>
Fri, 22 Dec 2017 14:19:59 +0000 (14:19 +0000)
committerChris Wilson <chris@chris-wilson.co.uk>
Fri, 22 Dec 2017 18:34:05 +0000 (18:34 +0000)
commit2d453c7895c0ca6028500050ff9305c70fd7252f
tree1c9def2aee240b0780be2c0772db95d4b31d0bdd
parent193a98dc7cc4770580ebcd0fa64a6c23a50093af
drm/i915: Assert that the request is on the execution queue before being removed

We should only attempt to remove requests from the execution queue that
are on the execution queue. These are the requests that have been
assigned a global_seqno, so we can assert that we only attempt to remove
requests with a nonzero global_seqno. Afterwards we assert that we
remove them in order, i.e. the global_seqno matches the engine's seqno,
but that leaves a small loophole for an unattached request on an unused
engine.

We can then make the same assertion on queuing the request to the
execution engine, it must have a zero global_seqno or else we are queuing
the same request twice.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: MichaƂ Winiarski <michal.winiarski@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171222141959.3006-1-chris@chris-wilson.co.uk
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
drivers/gpu/drm/i915/i915_gem_request.c