From: Ben Widawsky <ben@bwidawsk.net>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, miku@iki.fi
Subject: Re: [PATCH 5/5] drm/i915: remove i915_hangcheck_hung
Date: Wed, 29 May 2013 10:48:39 -0700 [thread overview]
Message-ID: <20130529174839.GA13819@bwidawsk.net> (raw)
In-Reply-To: <1368451933-32571-5-git-send-email-mika.kuoppala@intel.com>
On Mon, May 13, 2013 at 04:32:13PM +0300, Mika Kuoppala wrote:
> Rework of per ring hangcheck made this obsolete.
>
>
>
Probably could have put this in the last patch. Assuming you add the
comment on #4, and Daniel/Chris are okay with the proposed functional
change, 4 & 5 are:
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.h | 1 -
> drivers/gpu/drm/i915/i915_irq.c | 21 ---------------------
> 2 files changed, 22 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index db7cda9..3161d33 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -833,7 +833,6 @@ struct i915_gpu_error {
> #define DRM_I915_HANGCHECK_PERIOD 1500 /* in ms */
> #define DRM_I915_HANGCHECK_JIFFIES msecs_to_jiffies(DRM_I915_HANGCHECK_PERIOD)
> struct timer_list hangcheck_timer;
> - int hangcheck_count;
>
> /* For reset and error_state handling. */
> spinlock_t lock;
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 5dde61f..f204d83 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -2357,27 +2357,6 @@ static bool i915_hangcheck_ring_hung(struct intel_ring_buffer *ring)
> return !kick_ring(ring);
> }
>
> -static bool i915_hangcheck_hung(struct drm_device *dev)
> -{
> - drm_i915_private_t *dev_priv = dev->dev_private;
> -
> - if (dev_priv->gpu_error.hangcheck_count++ > 1) {
> - bool hung = true;
> - struct intel_ring_buffer *ring;
> - int i;
> -
> - DRM_ERROR("Hangcheck timer elapsed... GPU hung\n");
> - i915_handle_error(dev, true);
> -
> - for_each_ring(ring, dev_priv, i)
> - hung &= i915_hangcheck_ring_hung(ring);
> -
> - return hung;
> - }
> -
> - return false;
> -}
> -
> /**
> * This is called when the chip hasn't reported back with completed
> * batchbuffers in a long time. We keep track per ring seqno progress and
> --
> 1.7.9.5
>
--
Ben Widawsky, Intel Open Source Technology Center
prev parent reply other threads:[~2013-05-29 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 13:32 [PATCH 1/5] drm/i915: pass seqno to i915_hangcheck_ring_idle Mika Kuoppala
2013-05-13 13:32 ` [PATCH 2/5] drm/i915: track ring progression using seqnos Mika Kuoppala
2013-05-17 17:40 ` Ben Widawsky
2013-05-24 14:16 ` [PATCH 02/14] " Mika Kuoppala
2013-05-13 13:32 ` [PATCH 3/5] drm/i915: introduce i915_hangcheck_ring_hung Mika Kuoppala
2013-05-24 18:26 ` Ben Widawsky
2013-05-25 11:26 ` Daniel Vetter
2013-05-13 13:32 ` [PATCH 4/5] drm/i915: detect hang using per ring hangcheck_score Mika Kuoppala
2013-05-27 1:34 ` Ben Widawsky
2013-05-27 17:42 ` Mika Kuoppala
2013-05-30 6:04 ` [PATCH] " Mika Kuoppala
2013-05-13 13:32 ` [PATCH 5/5] drm/i915: remove i915_hangcheck_hung Mika Kuoppala
2013-05-29 17:48 ` Ben Widawsky [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=20130529174839.GA13819@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=miku@iki.fi \
/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