[Intel-gfx] [PATCH 2/6] drm/i915/vlv: Added a rendering specific Hw WA 'WaReadAfterWriteHazard'

[Gupta, Sourab]

On Wed, 2014-01-22 at 11:11 +0000, Chris Wilson wrote:
> On Wed, Jan 22, 2014 at 12:54:51PM +0200, Ville Syrjälä wrote:
> > On Wed, Jan 22, 2014 at 09:15:06AM +0530, akash.goel at intel.com wrote:
> > > From: Akash Goel <akash.goel at intel.com>
> > >
> > > Added a new rendering specific Workaround 'WaReadAfterWriteHazard'.
> > > In this WA, need to add 12 MI Store Dword commands to ensure proper
> > > flush of h/w pipeline.
> > >
> > > Signed-off-by: Akash Goel <akash.goel at intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/intel_ringbuffer.c | 25 +++++++++++++++++++++++++
> > >  1 file changed, 25 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > index 133d273..e8ec536 100644
> > > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > > @@ -2167,6 +2167,31 @@ intel_ring_flush_all_caches(struct intel_ring_buffer *ring)
> > >
> > >     trace_i915_gem_ring_flush(ring, 0, I915_GEM_GPU_DOMAINS);
> > >
> > > +   if (IS_VALLEYVIEW(ring->dev)) {
> > > +           /*
> > > +            * WaReadAfterWriteHazard
> > > +            * Send a number of Store Data commands here to finish
> > > +            * flushing hardware pipeline.This is needed in the case
> > > +            * where the next workload tries reading from the same
> > > +            * surface that this batch writes to. Without these StoreDWs,
> > > +            * not all of the data will actually be flushd to the surface
> > > +            * by the time the next batch starts reading it, possibly
> > > +            * causing a small amount of corruption.
> > > +            */
> > > +           int i;
> > > +           ret = intel_ring_begin(ring, 4 * 12);
> >
> > BSpec says 8 is enough. Is Bspec incorrect.
> 
> No, these are just figures they plucked out of the air. Last I heard
> they were using 32...
> 
> > Also this workaround is also listed for everything SNB+.
> 
> And we already have a more effective workaround.
> -Chris

Can you please let us know whether this workaround patch is required or
not. If not, then how is this currently handled.
> 
> --
> Chris Wilson, Intel Open Source Technology Centre