From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/i915: Remove BXT incoherent seqno write workaround
Date: Mon, 23 Jan 2017 15:43:27 +0200 [thread overview]
Message-ID: <20170123134327.GM31595@intel.com> (raw)
In-Reply-To: <20170123130601.2281-2-chris@chris-wilson.co.uk>
On Mon, Jan 23, 2017 at 01:05:57PM +0000, Chris Wilson wrote:
> This w/a was only used for preproduction hw, which is no longer in use.
> Remove the workaround to simplify the code.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/intel_lrc.c | 17 -----------------
> 1 file changed, 17 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
> index 8ffa4961aa40..202ce1e6e499 100644
> --- a/drivers/gpu/drm/i915/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/intel_lrc.c
> @@ -1638,21 +1638,6 @@ static int gen8_emit_flush_render(struct drm_i915_gem_request *request,
> return 0;
> }
>
> -static void bxt_a_seqno_barrier(struct intel_engine_cs *engine)
> -{
> - /*
> - * On BXT A steppings there is a HW coherency issue whereby the
> - * MI_STORE_DATA_IMM storing the completed request's seqno
> - * occasionally doesn't invalidate the CPU cache. Work around this by
> - * clflushing the corresponding cacheline whenever the caller wants
> - * the coherency to be guaranteed. Note that this cacheline is known
> - * to be clean at this point, since we only write it in
> - * bxt_a_set_seqno(), where we also do a clflush after the write. So
> - * this clflush in practice becomes an invalidate operation.
> - */
> - intel_flush_status_page(engine, I915_GEM_HWS_INDEX);
> -}
Ahem. Don't we have hardware in the pipeline which is going to need
this stuff?
> -
> /*
> * Reserve space for 2 NOOPs at the end of each request to be
> * used as a workaround for not being allowed to do lite
> @@ -1800,8 +1785,6 @@ logical_ring_default_vfuncs(struct intel_engine_cs *engine)
> engine->irq_enable = gen8_logical_ring_enable_irq;
> engine->irq_disable = gen8_logical_ring_disable_irq;
> engine->emit_bb_start = gen8_emit_bb_start;
> - if (IS_BXT_REVID(engine->i915, 0, BXT_REVID_A1))
> - engine->irq_seqno_barrier = bxt_a_seqno_barrier;
> }
>
> static inline void
> --
> 2.11.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-23 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:05 [PATCH 1/6] drm/i915: Remove disable_lite_restore_wa Chris Wilson
2017-01-23 13:05 ` [PATCH 2/6] drm/i915: Remove BXT incoherent seqno write workaround Chris Wilson
2017-01-23 13:38 ` Joonas Lahtinen
2017-01-23 13:43 ` Ville Syrjälä [this message]
2017-01-23 13:52 ` Chris Wilson
2017-01-23 14:35 ` Ville Syrjälä
2017-01-23 13:05 ` [PATCH 3/6] drm/i915: Remove BXT restore arbitration around ctx switch Chris Wilson
2017-01-23 13:10 ` Joonas Lahtinen
2017-01-23 13:05 ` [PATCH 4/6] drm/i915: Remove BXT disable pixel mask clamping w/a Chris Wilson
2017-01-23 13:39 ` Joonas Lahtinen
2017-01-23 13:06 ` [PATCH 5/6] drm/i915: Remove BXT TDL state w/a Chris Wilson
2017-01-23 13:16 ` Joonas Lahtinen
2017-01-23 13:06 ` [PATCH 6/6] drm/i915: Remove unused per-bb wa_ctx for gen9 Chris Wilson
2017-01-23 13:09 ` [PATCH 1/6] drm/i915: Remove disable_lite_restore_wa Joonas Lahtinen
2017-01-23 13:13 ` Chris Wilson
2017-01-23 13:52 ` ✓ Fi.CI.BAT: success for series starting with [1/6] " 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=20170123134327.GM31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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