drm/i915: Update ring position from request on retiring
authorChris Wilson <chris@chris-wilson.co.uk>
Wed, 7 Mar 2018 13:42:23 +0000 (13:42 +0000)
committerChris Wilson <chris@chris-wilson.co.uk>
Fri, 9 Mar 2018 14:13:31 +0000 (14:13 +0000)
When wedged, we do not update the ring->tail as we submit the requests
causing us to leak the ring->space upon cleaning up the wedged driver.
We can just use the value stored in rq->tail, and keep the submission
backend details away from set-wedge.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180307134226.25492-3-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/i915_request.c
drivers/gpu/drm/i915/intel_ringbuffer.c

index d437beac3969f815c7e8c8430cd7c590d2bba2a6..75c8826c8cae9e8ae45ed42cd7bbbbd221195fdd 100644 (file)
@@ -358,7 +358,7 @@ static void advance_ring(struct i915_request *request)
                 * is just about to be. Either works, if we miss the last two
                 * noops - they are safe to be replayed on a reset.
                 */
-               tail = READ_ONCE(request->ring->tail);
+               tail = READ_ONCE(request->tail);
        } else {
                tail = request->postfix;
        }
index 1d599524a75900559aca8f571dd257347233ec90..88eeb64041ae1f6f0107869300bc6245c5c628e3 100644 (file)
@@ -1593,6 +1593,7 @@ static noinline int wait_for_space(struct intel_ring *ring, unsigned int bytes)
        if (intel_ring_update_space(ring) >= bytes)
                return 0;
 
+       GEM_BUG_ON(list_empty(&ring->request_list));
        list_for_each_entry(target, &ring->request_list, ring_link) {
                /* Would completion of this request free enough space? */
                if (bytes <= __intel_ring_space(target->postfix,