public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fixup hangman rebase goof-up
Date: Sat, 16 Jun 2012 16:10:31 +0100	[thread overview]
Message-ID: <1339859448_30750@CP5-2952> (raw)
In-Reply-To: <CAKMK7uFJBk2fXvdCofYf51w8Y-As84XBnr6SF8V48KbRJrietA@mail.gmail.com>

On Sat, 16 Jun 2012 17:04:27 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Sat, Jun 16, 2012 at 4:57 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Sat, 16 Jun 2012 16:42:05 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >> I've added a bit of logic such that running the hangman test on chips
> >> without any hw reset support at all doesn't wedge the gpu because the
> >> reset failed. This relied on checking for non-null stop_rings.
> >> Unfortunately I've botched a rebase somewhere and stop_rings is still
> >> cleared at the old place before the reset code.
> >>
> >> Fix this up so that running the i-g-t tests on gen2/3 doesn't result
> >> in a wedged gpu.
> >
> > dev_priv->stop_rings = 0; is there on both dif and dinq. An unpushed
> > mistake perhaps?
> 
> Well, the hangman got merged for 3.5 and has been broken since then.
> Yeah, shame on me for not noticing earlier :(
> 
> This came about that stop_rings = 0 as removed by this patch was the
> earlier place if reset it. But to not wedge the gpu I need to still
> know whether this is a simulated gpu hang after the reset code ran and
> failed with -ENODEV (indicating the missing reset code). The right
> code is in intel_gpu_reset. I've tested before submitting the patches,
> but somehow managed to slip in the old hunk somehow in a last-minute
> rebase.
> 
> This patch just kills this spurious hunk.

...but this patches adds the existing line...

* confused.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-06-16 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 14:42 [PATCH] drm/i915: fixup hangman rebase goof-up Daniel Vetter
2012-06-16 14:57 ` Chris Wilson
2012-06-16 15:04   ` Daniel Vetter
2012-06-16 15:10     ` Chris Wilson [this message]
2012-06-16 16:29       ` Daniel Vetter
2012-06-18  8:37         ` Daniel Vetter

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=1339859448_30750@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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