From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH 2/4] drm/i915: Only slightly increment hangcheck score if we succesfully kick a ring
Date: Tue, 11 Jun 2013 16:05:41 +0200 [thread overview]
Message-ID: <20130611140541.GX22870@phenom.ffwll.local> (raw)
In-Reply-To: <20130611134019.GA32097@cantiga.alporthouse.com>
On Tue, Jun 11, 2013 at 02:40:19PM +0100, Chris Wilson wrote:
> On Tue, Jun 11, 2013 at 11:45:00AM +0200, Daniel Vetter wrote:
> > On Mon, Jun 10, 2013 at 11:20:20AM +0100, Chris Wilson wrote:
> > > + if (ring->hangcheck.seqno == seqno) {
> > > + if (ring_idle(ring, seqno)) {
> > > + if (waitqueue_active(&ring->irq_queue)) {
> > > + /* Issue a wake-up to catch stuck h/w. */
> > > + DRM_ERROR("Hangcheck timer elapsed... %s idle\n",
> > > + ring->name);
> > > + wake_up_all(&ring->irq_queue);
> > > + ring->hangcheck.score += HUNG;
> >
> > Not sure whether we want to hit missed interrupts this badly, it was
> > rather common a while back ;-) But we can fine-tune this easily now, so
> > now reservations for merging from my side.
>
> Not sure what you mean here. The check is fairly easy and has gotten us
> out of many a hole before, and makes for a good defense. So how would
> you want to fine tune it?
Something like the MI_WAIT hangcheck score, but like I've said as long as
we don't have a real-world bug report (some poor guy disabled semaphores
maybe due to the snb issue?) not worth bothering at all.
I've just thought that if we're unlucky and miss the interrupt a few times
in a row we don't want to accidentally declare the gpu dead.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-06-11 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 10:20 [PATCH 1/4] drm/i915: Initialize ring->hangcheck upon ring init Chris Wilson
2013-06-10 10:20 ` [PATCH 2/4] drm/i915: Only slightly increment hangcheck score if we succesfully kick a ring Chris Wilson
2013-06-11 9:45 ` Daniel Vetter
2013-06-11 13:40 ` Chris Wilson
2013-06-11 14:05 ` Daniel Vetter [this message]
2013-06-11 14:16 ` Chris Wilson
2013-06-11 14:37 ` Daniel Vetter
2013-06-11 16:10 ` Chris Wilson
2013-06-10 10:20 ` [PATCH 3/4] drm/i915: Don't count semaphore waits towards a stuck ring Chris Wilson
2013-06-11 9:51 ` Daniel Vetter
2013-06-10 10:20 ` [PATCH 4/4] drm/i915: Eliminate the addr/seqno from the hangcheck warning Chris Wilson
2013-06-10 13:42 ` 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=20130611140541.GX22870@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--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