public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Revert workaround for disabling L3 cache aging on BYT
Date: Tue, 4 Mar 2014 16:47:52 +0100	[thread overview]
Message-ID: <20140304154752.GJ17001@phenom.ffwll.local> (raw)
In-Reply-To: <20140220081839.2e75142d@jbarnes-desktop>

On Thu, Feb 20, 2014 at 08:18:39AM -0800, Jesse Barnes wrote:
> On Wed, 19 Feb 2014 13:09:31 -0800
> Sinclair Yeh <sinclair.yeh@intel.com> wrote:
> 
> > V2:  edit the commit message to contain more info
> > The W/A spreadsheet says this is still required, but the b-spec says
> > it's not for BYT-T.  So the documentation is not clear.  However,
> > our experience with the other SKUs of BYT-I/M on Android and Linux
> > suggests that setting this bit actually causes GPU hang for certain
> > OGL benchmark applications.
> > 
> > Removing this bit completely resolves the GPU hangs.

Your sob is missing. Please see the developer's certificate of origin so
that you're aware of what you actually sign off on. Since you work for the
same company I've snuck this in ;-)

> > ---
> >  drivers/gpu/drm/i915/intel_pm.c | 3 ---
> >  1 file changed, 3 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index a6b877a..3ba037e 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -5004,9 +5004,6 @@ static void valleyview_init_clock_gating(struct drm_device *dev)
> >  		   _MASKED_BIT_ENABLE(GEN7_MAX_PS_THREAD_DEP |
> >  				      GEN7_PSD_SINGLE_PORT_DISPATCH_ENABLE));
> >  
> > -	/* WaDisableL3CacheAging:vlv */
> > -	I915_WRITE(GEN7_L3CNTLREG1, I915_READ(GEN7_L3CNTLREG1) | GEN7_L3AGDIS);
> > -
> >  	/* WaForceL3Serialization:vlv */
> >  	I915_WRITE(GEN7_L3SQCREG4, I915_READ(GEN7_L3SQCREG4) &
> >  		   ~L3SQ_URB_READ_CAM_MATCH_DISABLE);
> 
> I don't think we have good docs on this, but since it works empirically:
> 
> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-03-04 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 22:13 [PATCH] Fix GPU Hang on BYT Sinclair Yeh
2014-02-19 21:09 ` [PATCH] drm/i915: Revert workaround for disabling L3 cache aging " Sinclair Yeh
2014-02-20 16:18   ` Jesse Barnes
2014-03-04 15:47     ` 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=20140304154752.GJ17001@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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