From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't continually defer the hangcheck
Date: Fri, 07 Nov 2014 16:28:33 +0200 [thread overview]
Message-ID: <87y4rnkru6.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <1415353627-21854-1-git-send-email-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> With multiple rings, we may continue to render on the blitter whilst
> executing an infinite shader on the render ring. As we currently, rearm
> the timer with each execbuf, in this scenario the hangcheck will never
> fire and we will never detect the lockup on the render ring. Instead,
> only arm the timer once per hangcheck, so that hangcheck runs more
> frequently.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/i915_irq.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 318a6a0724d0..82b4d742aba5 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -3039,11 +3039,16 @@ static void i915_hangcheck_elapsed(unsigned long data)
> void i915_queue_hangcheck(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> + struct timer_list *timer = &dev_priv->gpu_error.hangcheck_timer;
> +
> if (!i915.enable_hangcheck)
> return;
>
> - mod_timer(&dev_priv->gpu_error.hangcheck_timer,
> - round_jiffies_up(jiffies + DRM_I915_HANGCHECK_JIFFIES));
> + if (timer_pending(timer))
> + return;
> +
As this is called from both process and interrupt context, what
keeps us safe from not messing up the timer bookkeepping? The lock in timer code?
I am thinking that the other thread will hit the BUG_ON in add_timer().
-Mika
> + timer->expires = round_jiffies_up(jiffies + DRM_I915_HANGCHECK_JIFFIES);
> + add_timer(timer);
> }
>
> static void ibx_irq_reset(struct drm_device *dev)
> --
> 2.1.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-07 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 9:47 [PATCH] drm/i915: Don't continually defer the hangcheck Chris Wilson
2014-11-07 14:28 ` Mika Kuoppala [this message]
2014-11-07 14:35 ` Chris Wilson
2014-11-07 15:14 ` Mika Kuoppala
2014-11-19 10:00 ` Daniel Vetter
2014-11-19 10:13 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2014-11-19 9:47 Chris Wilson
2014-11-19 10:43 ` Mika Kuoppala
2014-11-19 10:45 ` Daniel Vetter
2014-11-19 17:05 ` shuang.he
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=87y4rnkru6.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