From: Ben Widawsky <benjamin.widawsky@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] [v2] drm/i915: Limit VF cache invalidate workaround usage to gen9
Date: Thu, 17 Dec 2015 13:39:22 -0800 [thread overview]
Message-ID: <20151217213921.GA29902@intel.com> (raw)
In-Reply-To: <1450385364.2449.9.camel@intel.com>
On Thu, Dec 17, 2015 at 10:49:24PM +0200, Imre Deak wrote:
> On Thu, 2015-12-17 at 09:49 -0800, Ben Widawsky wrote:
> > It is unclear if this is even required on BXT.
>
> I'm not sure either, I only added it on the premise that it was marked
> as SKL+ originally in BSpec. The revision log entry in BSpec has this
> much to say:
> """
> The workaround that requires an empty PIPE_CONTROL before a
> PIPE_CONTROL with a VF Cache Invalidation Enable is only for SKL and
> not SKL+. The bug was fixed in CNL with the following HSD:...
> """
> Which doesn't make this clear either imo.
>
> > v2: Make sure to set the default value to false. Uncertain how my compiler
> > doesn't complain with v1.
> >
> > Cc: Imre Deak <imre.deak@intel.com>
> > Signed-off-by: Ben Widawsky <benjamin.widawsky@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_lrc.c | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
> > index 519cea32..af1e001 100644
> > --- a/drivers/gpu/drm/i915/intel_lrc.c
> > +++ b/drivers/gpu/drm/i915/intel_lrc.c
> > @@ -1695,7 +1695,7 @@ static int gen8_emit_flush_render(struct drm_i915_gem_request *request,
> > struct intel_ringbuffer *ringbuf = request->ringbuf;
> > struct intel_engine_cs *ring = ringbuf->ring;
> > u32 scratch_addr = ring->scratch.gtt_offset + 2 * CACHELINE_BYTES;
> > - bool vf_flush_wa;
> > + bool vf_flush_wa = false;
> > u32 flags = 0;
> > int ret;
> >
> > @@ -1716,14 +1716,14 @@ static int gen8_emit_flush_render(struct drm_i915_gem_request *request,
> > flags |= PIPE_CONTROL_STATE_CACHE_INVALIDATE;
> > flags |= PIPE_CONTROL_QW_WRITE;
> > flags |= PIPE_CONTROL_GLOBAL_GTT_IVB;
> > - }
> >
> > - /*
> > - * On GEN9+ Before VF_CACHE_INVALIDATE we need to emit a NULL pipe
> > - * control.
> > - */
> > - vf_flush_wa = INTEL_INFO(ring->dev)->gen >= 9 &&
> > - flags & PIPE_CONTROL_VF_CACHE_INVALIDATE;
> > + /*
> > + * On GEN9: before VF_CACHE_INVALIDATE we need to emit a NULL
> > + * pipe control.
> > + */
> > +> if (IS_GEN9(ring->dev))
>
> Nitpick: INTEL_INFO()->gen == 9 is the preferred way. Either way:
> Reviewed-by: Imre Deak <imre.deak@intel.com>
>
Sounds good to me. Does someone mind fixing this up when they push? This patch
is a pre-requisite to another internal patch I have at the moment.
> > + vf_flush_wa = true;
> > + }
> >
> > ret = intel_logical_ring_begin(request, vf_flush_wa ? 12 : 6);
> > if (ret)
--
Ben Widawsky, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-17 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 1:51 [PATCH] drm/i915: Limit VF cache invalidate workaround usage to gen9 Ben Widawsky
2015-12-17 17:49 ` [PATCH] [v2] " Ben Widawsky
2015-12-17 20:49 ` Imre Deak
2015-12-17 21:39 ` Ben Widawsky [this message]
2015-12-18 9:59 ` Jani Nikula
2015-12-18 10:34 ` Imre Deak
2015-12-21 12:05 ` Daniel Vetter
2015-12-21 12:06 ` Daniel Vetter
2015-12-18 7:20 ` ✗ warning: Fi.CI.BAT Patchwork
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=20151217213921.GA29902@intel.com \
--to=benjamin.widawsky@intel.com \
--cc=imre.deak@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).