From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/chv: Add additional workarounds for CHV
Date: Thu, 4 Dec 2014 12:12:25 +0100 [thread overview]
Message-ID: <20141204111225.GA20350@phenom.ffwll.local> (raw)
In-Reply-To: <20141204105840.GB10649@intel.com>
On Thu, Dec 04, 2014 at 12:58:40PM +0200, Ville Syrjälä wrote:
> On Wed, Dec 03, 2014 at 07:15:31PM +0000, Arun Siluvery wrote:
> > These w/a were recently identified while debugging another issue,
> > +WaClearFlowControlGpgpuContextSave:chv
> > +Wa4x4STCOptimizationDisable:chv
> >
> > For: VIZ-4090
> > Change-Id: I08d2176dec609396c3a7c2e48b2413e233799fc4
> > Signed-off-by: Arun Siluvery <arun.siluvery@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_reg.h | 1 +
> > drivers/gpu/drm/i915/intel_ringbuffer.c | 5 +++++
> > 2 files changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index dc03fac..7c7663f 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -6131,6 +6131,7 @@ enum punit_power_well {
> > #define GEN9_DG_MIRROR_FIX_ENABLE (1<<5)
> >
> > #define GEN8_ROW_CHICKEN 0xe4f0
> > +#define FLOW_CONTROL_ENABLE (1<<15)
> > #define PARTIAL_INSTRUCTION_SHOOTDOWN_DISABLE (1<<8)
> > #define STALL_DOP_GATING_DISABLE (1<<5)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 79b4ca5..525c9bf 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -796,8 +796,10 @@ static int chv_init_workarounds(struct intel_engine_cs *ring)
> >
> > /* WaDisablePartialInstShootdown:chv */
> > /* WaDisableThreadStallDopClockGating:chv */
> > + /* WaClearFlowControlGpgpuContextSave:chv */
> > WA_SET_BIT_MASKED(GEN8_ROW_CHICKEN,
> > PARTIAL_INSTRUCTION_SHOOTDOWN_DISABLE |
> > + FLOW_CONTROL_ENABLE |
>
> This seems to be the default value already. I suppose there's no real
> harm in setting it though, but then we should also do the same for BDW.
>
> Would be nice if we actually did a GPU reset on driver load to guarantee
> a more consistent initial state...
We have some half-baked testcase to compare the different wa registers
states after driver load, reset and suspend/resume. But that's not yet
been fixed up to also take all the static wa settings into account.
Would be awesome if that would finally happen.
/me dreaming ;-)
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-04 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 19:15 [PATCH] drm/i915/chv: Add additional workarounds for CHV Arun Siluvery
2014-12-04 10:58 ` Ville Syrjälä
2014-12-04 11:12 ` Daniel Vetter [this message]
2014-12-05 1:10 ` shuang.he
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=20141204111225.GA20350@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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