From: Andi Shyti <andi.shyti@linux.intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com,
gregory.f.germano@intel.com, matthew.d.roper@intel.com,
tomasz.mistat@intel.com, nirmoy.das@intel.com
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915: Add WABB blit for Wa_16018031267 / Wa_16018063123
Date: Thu, 24 Aug 2023 16:53:41 +0200 [thread overview]
Message-ID: <ZOdu9dtMSeoErFFx@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230823185104.1994138-2-jonathan.cavitt@intel.com>
Hi Jonathan,
few little things...
On Wed, Aug 23, 2023 at 11:51:03AM -0700, Jonathan Cavitt wrote:
> From: Nirmoy Das <nirmoy.das@intel.com>
>
> Apply WABB blit for Wa_16018031267 / Wa_16018063123.
> Additionally, update the lrc selftest to exercise the new
> WABB changes.
>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Co-developed-by: Nirmoy Das <nirmoy.das@intel.com>
As the sender of this patch, your SoB should be last and you also
need to add Nirmoy's SoB above yours.
(Tags should be added in chronological order)
[...]
> +static u32 *
> +xehp_emit_per_ctx_bb(const struct intel_context *ce, u32 *cs)
> +{
> + /* Wa_16018031267, Wa_16018063123 */
> + if (ce->engine->class == COPY_ENGINE_CLASS &&
> + NEEDS_FASTCOLOR_BLT_WABB(ce->engine->i915))
> + cs = xehp_emit_fastcolor_blt_wabb(ce, cs);
I thought the trend was to have things like:
..._needs_wa_16018031267()
But we don't have a unified system yet
> + return cs;
> +}
> +
> +
two blank lines here
> +static void
> +setup_per_ctx_bb(const struct intel_context *ce,
> + const struct intel_engine_cs *engine,
> + u32 *(*emit)(const struct intel_context *, u32 *))
> +{
[...]
> static u32 *
> -emit_indirect_ctx_bb_canary(const struct intel_context *ce, u32 *cs)
> +emit_wabb_ctx_canary(const struct intel_context *ce,
> + u32 *cs, bool per_ctx)
just a little alignment issue here.
> {
[...]
Are the failures from CI coming from this series?
Andi
next prev parent reply other threads:[~2023-08-24 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 18:51 [Intel-gfx] [PATCH v2 0/2] Apply Wa_16018031267 / Wa_16018063123 Jonathan Cavitt
2023-08-23 18:51 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: Add WABB blit for " Jonathan Cavitt
2023-08-24 14:53 ` Andi Shyti [this message]
2023-08-24 15:01 ` Cavitt, Jonathan
2023-08-24 17:57 ` Matt Roper
2023-08-23 18:51 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: Set copy engine arbitration " Jonathan Cavitt
2023-08-24 14:57 ` Andi Shyti
2023-08-23 21:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Apply Wa_16018031267 / Wa_16018063123 (rev2) Patchwork
2023-08-23 21:15 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-23 21:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-24 21:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Apply Wa_16018031267 / Wa_16018063123 (rev3) Patchwork
2023-08-24 21:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-24 21:24 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=ZOdu9dtMSeoErFFx@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=gregory.f.germano@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tomasz.mistat@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.