From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/7] drm/i915: Add Wa_1207131216:icl,ehl
Date: Tue, 10 Mar 2020 18:22:36 +0200 [thread overview]
Message-ID: <87a74o5gdv.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200310004911.1723239-3-matthew.d.roper@intel.com>
Matt Roper <matthew.d.roper@intel.com> writes:
> On gen11 the XY_FAST_COPY_BLT command has some size restrictions on its
> usage. Although this instruction is mainly used by userspace, i915 also
> uses it to copy object contents during some selftests, so let's ensure
> the restrictions are followed.
>
> Bspec: 6544
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_object_blt.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_object_blt.c b/drivers/gpu/drm/i915/gem/i915_gem_object_blt.c
> index 39b8a055d80a..e00792158f13 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_object_blt.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_object_blt.c
> @@ -196,6 +196,17 @@ int i915_gem_object_fill_blt(struct drm_i915_gem_object *obj,
> return err;
> }
>
> +/* Wa_1209644611:icl,ehl */
> +static bool wa_1209644611_applies(struct drm_i915_private *i915, u32 size)
> +{
> + u32 height = size >> PAGE_SHIFT;
> +
> + if (!IS_GEN(i915, 11))
> + return false;
> +
> + return height % 4 == 3 && height <= 8;
The workaround description matches with this. However the original
sighting was only for Y-Tiled surfaces. I asked for clarification.
If we won't get one, we can play it safe and use this as it is.
-Mika
> +}
> +
> struct i915_vma *intel_emit_vma_copy_blt(struct intel_context *ce,
> struct i915_vma *src,
> struct i915_vma *dst)
> @@ -237,7 +248,8 @@ struct i915_vma *intel_emit_vma_copy_blt(struct intel_context *ce,
> size = min_t(u64, rem, block_size);
> GEM_BUG_ON(size >> PAGE_SHIFT > S16_MAX);
>
> - if (INTEL_GEN(i915) >= 9) {
> + if (INTEL_GEN(i915) >= 9 &&
> + !wa_1209644611_applies(i915, size)) {
> *cmd++ = GEN9_XY_FAST_COPY_BLT_CMD | (10 - 2);
> *cmd++ = BLT_DEPTH_32 | PAGE_SIZE;
> *cmd++ = 0;
> --
> 2.24.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-10 16:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 0:49 [Intel-gfx] [PATCH 0/7] Gen11 workarounds Matt Roper
2020-03-10 0:49 ` [Intel-gfx] [PATCH 1/7] drm/i915: Handle all MCR ranges Matt Roper
2020-03-10 0:49 ` [Intel-gfx] [PATCH 2/7] drm/i915: Add Wa_1207131216:icl,ehl Matt Roper
2020-03-10 16:22 ` Mika Kuoppala [this message]
2020-03-10 0:49 ` [Intel-gfx] [PATCH 3/7] drm/i915: Add Wa_1604278689:icl,ehl Matt Roper
2020-03-10 16:37 ` Chris Wilson
2020-03-10 16:49 ` Matt Roper
2020-03-10 0:49 ` [Intel-gfx] [PATCH 4/7] drm/i915: Add Wa_1406306137:icl,ehl Matt Roper
2020-03-10 0:49 ` [Intel-gfx] [PATCH 5/7] drm/i915: Apply Wa_1406680159:icl, ehl as an engine workaround Matt Roper
2020-03-10 0:49 ` [Intel-gfx] [PATCH 6/7] drm/i915: Add Wa_1605460711 / Wa_1408767742 to ICL and EHL Matt Roper
2020-03-10 0:49 ` [Intel-gfx] [PATCH 7/7] drm/i915: Add Wa_1409178092:icl,ehl Matt Roper
2020-03-10 1:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Gen11 workarounds Patchwork
2020-03-10 17:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-10 22:28 ` Souza, Jose
2020-03-10 23:18 ` Matt Roper
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=87a74o5gdv.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 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.