From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/i915: Reset ring space estimate after unwinding the request
Date: Fri, 09 Mar 2018 15:17:09 +0200 [thread overview]
Message-ID: <876065o0bu.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20180307134226.25492-2-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> With a series of unusual events (a sequence of interrupted request
> allocations), we could gradually leak the ring->space estimate by
> unwinding the ring back to the start of the request, but not return the
> used space back to the ring. Eventually and with great misfortune, it
> would be possible to trigger ring->space exhaustion with no requests on
> the ring.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_request.c | 1 +
> drivers/gpu/drm/i915/intel_ringbuffer.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index d437beac3969..efa9ee557f31 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -798,6 +798,7 @@ i915_request_alloc(struct intel_engine_cs *engine, struct i915_gem_context *ctx)
>
> err_unwind:
> rq->ring->emit = rq->head;
> + intel_ring_update_space(rq->ring);
>
> /* Make sure we didn't add ourselves to external state before freeing */
> GEM_BUG_ON(!list_empty(&rq->active_list));
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 1d599524a759..88eeb64041ae 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -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));
At some point, after long series of misfortunate events, we
will add a first request and need actually wait a space for this
and then we kaboom in here?
-Mika
> 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,
> --
> 2.16.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-09 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 13:42 [PATCH 1/6] drm/i915: Finish the wait-for-wedge by retiring all the inflight requests Chris Wilson
2018-03-07 13:42 ` [PATCH 2/6] drm/i915: Reset ring space estimate after unwinding the request Chris Wilson
2018-03-09 13:17 ` Mika Kuoppala [this message]
2018-03-09 13:42 ` Chris Wilson
2018-03-09 13:20 ` Chris Wilson
2018-03-07 13:42 ` [PATCH 3/6] drm/i915: Update ring position from request on retiring Chris Wilson
2018-03-09 13:38 ` Mika Kuoppala
2018-03-09 13:56 ` Chris Wilson
2018-03-07 13:42 ` [PATCH 4/6] drm/i915: Include ring->emit in debugging Chris Wilson
2018-03-09 13:41 ` Mika Kuoppala
2018-03-07 13:42 ` [PATCH 5/6] drm/i915: Wrap engine->schedule in RCU locks for set-wedge protection Chris Wilson
2018-03-09 13:49 ` Mika Kuoppala
2018-03-07 13:42 ` [PATCH 6/6] drm/i915: Only call tasklet_kill() on the first prepare_reset Chris Wilson
2018-03-09 14:01 ` Mika Kuoppala
2018-03-09 14:10 ` Chris Wilson
2018-03-09 14:22 ` Chris Wilson
2018-03-07 14:31 ` ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Finish the wait-for-wedge by retiring all the inflight requests Patchwork
2018-03-07 16:55 ` ✓ Fi.CI.IGT: " Patchwork
2018-03-09 12:54 ` [PATCH 1/6] " Mika Kuoppala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=876065o0bu.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox