From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Reorder semaphore deadlock check
Date: Tue, 10 Jun 2014 19:36:57 +0300 [thread overview]
Message-ID: <878up4u3fa.fsf@intel.com> (raw)
In-Reply-To: <871tv2qrqb.fsf@gaia.fi.intel.com>
On Fri, 06 Jun 2014, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
>> If a semaphore is waiting on another ring, which in turn happens to be
>> waiting on the first ring, but that second semaphore has been signalled,
>> we will be able to kick the second ring and so can treat the first ring
>> as a valid WAIT and not as HUNG.
>>
>> v2: Be paranoid and cap the potential recursion depth whilst visiting
>> the semaphore signallers. (Mika)
>>
>> References: https://bugs.freedesktop.org/show_bug.cgi?id=54226
>> References: https://bugs.freedesktop.org/show_bug.cgi?id=75502
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> Cc: stable@vger.kernel.org
>> ---
>
> Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
Pushed to -fixes, thanks for the patch and review.
BR,
Jani.
>
>> drivers/gpu/drm/i915/i915_irq.c | 18 ++++++++++++++----
>> drivers/gpu/drm/i915/intel_ringbuffer.h | 2 +-
>> 2 files changed, 15 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
>> index a702303eab08..2974698f8f27 100644
>> --- a/drivers/gpu/drm/i915/i915_irq.c
>> +++ b/drivers/gpu/drm/i915/i915_irq.c
>> @@ -2831,10 +2831,14 @@ static int semaphore_passed(struct intel_engine_cs *ring)
>> struct intel_engine_cs *signaller;
>> u32 seqno, ctl;
>>
>> - ring->hangcheck.deadlock = true;
>> + ring->hangcheck.deadlock++;
>>
>> signaller = semaphore_waits_for(ring, &seqno);
>> - if (signaller == NULL || signaller->hangcheck.deadlock)
>> + if (signaller == NULL)
>> + return -1;
>> +
>> + /* Prevent pathological recursion due to driver bugs */
>> + if (signaller->hangcheck.deadlock >= I915_NUM_RINGS)
>> return -1;
>>
>> /* cursory check for an unkickable deadlock */
>> @@ -2842,7 +2846,13 @@ static int semaphore_passed(struct intel_engine_cs *ring)
>> if (ctl & RING_WAIT_SEMAPHORE && semaphore_passed(signaller) < 0)
>> return -1;
>>
>> - return i915_seqno_passed(signaller->get_seqno(signaller, false), seqno);
>> + if (i915_seqno_passed(signaller->get_seqno(signaller, false), seqno))
>> + return 1;
>> +
>> + if (signaller->hangcheck.deadlock)
>> + return -1;
>> +
>> + return 0;
>> }
>>
>> static void semaphore_clear_deadlocks(struct drm_i915_private *dev_priv)
>> @@ -2851,7 +2861,7 @@ static void semaphore_clear_deadlocks(struct drm_i915_private *dev_priv)
>> int i;
>>
>> for_each_ring(ring, dev_priv, i)
>> - ring->hangcheck.deadlock = false;
>> + ring->hangcheck.deadlock = 0;
>> }
>>
>> static enum intel_ring_hangcheck_action
>> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.h b/drivers/gpu/drm/i915/intel_ringbuffer.h
>> index 24357c597b54..31c2aab8ad2c 100644
>> --- a/drivers/gpu/drm/i915/intel_ringbuffer.h
>> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.h
>> @@ -55,7 +55,7 @@ struct intel_ring_hangcheck {
>> u32 seqno;
>> int score;
>> enum intel_ring_hangcheck_action action;
>> - bool deadlock;
>> + int deadlock;
>> };
>>
>> struct intel_ringbuffer {
>> --
>> 2.0.0
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-06-10 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 10:25 [PATCH] drm/i915: Reorder semaphore deadlock check Chris Wilson
2014-06-06 9:22 ` Chris Wilson
2014-06-06 10:04 ` Mika Kuoppala
2014-06-10 16:36 ` Jani Nikula [this message]
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=878up4u3fa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=stable@vger.kernel.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