From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Drop the timeline->mutex as we wait for retirement
Date: Tue, 03 Mar 2020 16:06:36 +0200 [thread overview]
Message-ID: <87v9nl5y8j.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200303140009.1494819-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> As we have pinned the timeline (using tl->active_count), we can safely
> drop the tl->mutex as we wait for what we believe to be the final
> request on that timeline. This is useful for ensuring that we do not
> block the engine heartbeat by hogging the kernel_context's timeline on a
> dead GPU.
>
> References: https://gitlab.freedesktop.org/drm/intel/issues/1364
> Fixes: 058179e72e09 ("drm/i915/gt: Replace hangcheck by heartbeats")
> Fixes: f33a8a51602c ("drm/i915: Merge wait_for_timelines with retire_request")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gt_requests.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_requests.c b/drivers/gpu/drm/i915/gt/intel_gt_requests.c
> index 8a5054f21bf8..24c99d0838af 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_requests.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_requests.c
> @@ -147,24 +147,32 @@ long intel_gt_retire_requests_timeout(struct intel_gt *gt, long timeout)
>
> fence = i915_active_fence_get(&tl->last_request);
> if (fence) {
> + mutex_unlock(&tl->mutex);
> +
> timeout = dma_fence_wait_timeout(fence,
> interruptible,
> timeout);
> dma_fence_put(fence);
> +
> + /* Retirement is best effort */
> + if (!mutex_trylock(&tl->mutex)) {
> + active_count++;
> + goto out_active;
> + }
> }
> }
>
> if (!retire_requests(tl) || flush_submission(gt))
> active_count++;
> + mutex_unlock(&tl->mutex);
>
> - spin_lock(&timelines->lock);
> +out_active: spin_lock(&timelines->lock);
>
> - /* Resume iteration after dropping lock */
> + /* Resume list iteration after reacquiring spinlock */
Now it is in mint.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> list_safe_reset_next(tl, tn, link);
> if (atomic_dec_and_test(&tl->active_count))
> list_del(&tl->link);
>
> - mutex_unlock(&tl->mutex);
>
> /* Defer the final release to after the spinlock */
> if (refcount_dec_and_test(&tl->kref.refcount)) {
> --
> 2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-03 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 14:00 [Intel-gfx] [PATCH] drm/i915/gt: Drop the timeline->mutex as we wait for retirement Chris Wilson
2020-03-03 14:06 ` Mika Kuoppala [this message]
2020-03-03 16:48 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/gt: Drop the timeline->mutex as we wait for retirement (rev2) Patchwork
2020-03-03 17:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-03-03 13:07 [Intel-gfx] [PATCH] drm/i915/gt: Drop the timeline->mutex as we wait for retirement Chris Wilson
2020-03-03 13:40 ` Mika Kuoppala
2020-03-03 14:04 ` 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=87v9nl5y8j.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.