All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Paulo Zanoni <paulo.r.zanoni@intel.com>,
	Damien Lespiau <damien.lespiau@intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Don't deref pipe->cpu_transcoder in the hangcheck code
Date: Fri, 9 Aug 2013 10:38:59 +0200	[thread overview]
Message-ID: <20130809083859.GA21740@phenom.ffwll.local> (raw)
In-Reply-To: <20130808134423.GA29287@cantiga.alporthouse.com>

On Thu, Aug 08, 2013 at 02:44:23PM +0100, Chris Wilson wrote:
> On Thu, Aug 08, 2013 at 03:12:06PM +0200, Daniel Vetter wrote:
> > From: Chris Wilson <chris@chris-wilson.co.uk>
> > 
> > If we get an error event really early in the driver setup sequence,
> > which gen3 is especially prone to with various display GTT faults we
> > Oops. So try to avoid this.
> > 
> > Additionally with Haswell the transcoders are a separate bank of
> > registers from the pipes (4 transcoders, 3 pipes). In event of an
> > error, we want to be sure we have a complete and accurate picture of
> > the machine state, so record all the transcoders in addition to all
> > the active pipes.
> > 
> > This regression has been introduced in
> > 
> > commit 702e7a56af3780d8b3a717f698209bef44187bb0
> > Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Date:   Tue Oct 23 18:29:59 2012 -0200
> > 
> >     drm/i915: convert PIPECONF to use transcoder instead of pipe
> > 
> > Based on the patch "drm/i915: Dump all transcoder registers on error"
> > from Chris Wilson:
> > 
> > v2: Rebase so that we don't try to be clever and try to figure out the
> > cpu transcoder from hw state. That exercise should be done when we
> > analyze the error state offline.
> > 
> > The actual bugfix is to not call intel_pipe_to_cpu_transcoder in the
> > error state capture code in case the pipes aren't fully set up yet.
> > 
> > v3: Simplifiy the err->num_transcoders computation a bit. While at it
> > make the error capture stuff save on systems without a display block.
> > 
> > v4: Fix fail, spotted by Jani.
> > 
> > v5: Completely new commit message, cc: stable.
> > 
> > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Cc: Damien Lespiau <damien.lespiau@intel.com>
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=60021
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> Lgtm. We may have to modify transcoders[] to be more dynamic in future,
> but for now this works.
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Picked up for -fixes, thanks for the review.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-08-09  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 13:12 [PATCH] drm/i915: Don't deref pipe->cpu_transcoder in the hangcheck code Daniel Vetter
2013-08-08 13:40 ` Jani Nikula
2013-08-08 13:44 ` Chris Wilson
2013-08-09  8:38   ` Daniel Vetter [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=20130809083859.GA21740@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=damien.lespiau@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=paulo.r.zanoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.