All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gt: WaSetVfGuardbandPreemptionVertexCount (bdw/chv)
Date: Mon, 22 Jul 2019 16:55:39 +0100	[thread overview]
Message-ID: <7c12951d-44a6-dcc0-502e-ca75103503ea@linux.intel.com> (raw)
In-Reply-To: <20190722131830.14601-1-chris@chris-wilson.co.uk>



On 22/07/2019 14:18, Chris Wilson wrote:
> As a w/a for data corruption, we are told to set the preemption vertex
> count to 0x20 on boot. As it is a counter, once contexts are active we
> do not expect the value to be retained, so hide it from the wa-list
> verification.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/gt/intel_workarounds.c | 24 +++++++++++++++++++++
>   1 file changed, 24 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> index 704ace01e7f5..7628f8463317 100644
> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> @@ -647,6 +647,26 @@ int intel_engine_emit_ctx_wa(struct i915_request *rq)
>   	return 0;
>   }
>   
> +static void
> +gen8_gt_workarounds_init(struct drm_i915_private *i915,
> +			 struct i915_wa_list *wal)
> +{
> +	/* WaSetVfGuardbandPreemptionVertexCount:bdw,chv */
> +	wa_write_masked_or(wal, _MMIO(0x83A4), 0, 0xffff0020);

0x83a4 is listed in saved state for the context so have you tried 
putting it as a context workaround?

Regards,

Tvrtko

> +}
> +
> +static void
> +bdw_gt_workarounds_init(struct drm_i915_private *i915, struct i915_wa_list *wal)
> +{
> +	gen8_gt_workarounds_init(i915, wal);
> +}
> +
> +static void
> +chv_gt_workarounds_init(struct drm_i915_private *i915, struct i915_wa_list *wal)
> +{
> +	gen8_gt_workarounds_init(i915, wal);
> +}
> +
>   static void
>   gen9_gt_workarounds_init(struct drm_i915_private *i915, struct i915_wa_list *wal)
>   {
> @@ -907,6 +927,10 @@ gt_init_workarounds(struct drm_i915_private *i915, struct i915_wa_list *wal)
>   		bxt_gt_workarounds_init(i915, wal);
>   	else if (IS_SKYLAKE(i915))
>   		skl_gt_workarounds_init(i915, wal);
> +	else if (IS_CHERRYVIEW(i915))
> +		chv_gt_workarounds_init(i915, wal);
> +	else if (IS_BROADWELL(i915))
> +		bdw_gt_workarounds_init(i915, wal);
>   	else if (INTEL_GEN(i915) <= 8)
>   		return;
>   	else
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-07-22 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 13:18 [PATCH] drm/i915/gt: WaSetVfGuardbandPreemptionVertexCount (bdw/chv) Chris Wilson
2019-07-22 13:50 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-07-22 15:55 ` Tvrtko Ursulin [this message]
2019-07-22 16:09   ` [PATCH] " Chris Wilson
2019-07-22 17:07 ` ✓ Fi.CI.IGT: success for " 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=7c12951d-44a6-dcc0-502e-ca75103503ea@linux.intel.com \
    --to=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.