From: "Kalvala, Haridhar" <haridhar.kalvala@intel.com>
To: Radhakrishna Sripada <radhakrishna.sripada@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915/mtl: Extend Wa_16014892111 to MTL A-step
Date: Sun, 14 May 2023 16:29:15 +0530 [thread overview]
Message-ID: <b1b8fffa-06db-1087-a34b-2fa8c39830c4@intel.com> (raw)
In-Reply-To: <20230513021438.185352-1-radhakrishna.sripada@intel.com>
On 5/13/2023 7:44 AM, Radhakrishna Sripada wrote:
> The dg2 workaround which is used for performance tuning
> is needed for Meteorlake A-step.
>
> v2: Limit the WA for A-step
>
> Bspec: 68331
> Cc: Haridhar Kalvala <haridhar.kalvala@intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Gustavo Sousa <gustavo.sousa@intel.com>
> Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 81a96c52a92b..9c1007c44298 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -1370,7 +1370,9 @@ gen12_emit_indirect_ctx_rcs(const struct intel_context *ce, u32 *cs)
> cs, GEN12_GFX_CCS_AUX_NV);
>
> /* Wa_16014892111 */
> - if (IS_DG2(ce->engine->i915))
> + if (IS_DG2(ce->engine->i915) ||
> + IS_MTL_GRAPHICS_STEP(ce->engine->i915, M, STEP_A0, STEP_B0) ||
> + IS_MTL_GRAPHICS_STEP(ce->engine->i915, P, STEP_A0, STEP_B0))
> cs = dg2_emit_draw_watermark_setting(cs);
>
looks good to me.
Acked-by: Haridhar Kalvala <haridhar.kalvala@intel.com>
> return cs;
--
Regards,
Haridhar Kalvala
next prev parent reply other threads:[~2023-05-14 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 2:14 [Intel-gfx] [PATCH v2 1/2] drm/i915/mtl: Extend Wa_16014892111 to MTL A-step Radhakrishna Sripada
2023-05-13 2:14 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/mtl: Add MTL performance tuning changes Radhakrishna Sripada
2023-05-14 11:13 ` Kalvala, Haridhar
2023-05-15 14:47 ` Gustavo Sousa
2023-05-15 15:44 ` Sripada, Radhakrishna
2023-05-13 3:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/2] drm/i915/mtl: Extend Wa_16014892111 to MTL A-step Patchwork
2023-05-13 4:12 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-05-14 10:59 ` Kalvala, Haridhar [this message]
2023-05-15 14:44 ` [Intel-gfx] [PATCH v2 1/2] " Gustavo Sousa
2023-05-15 15:42 ` Sripada, Radhakrishna
2023-05-15 17:28 ` Matt Roper
2023-05-15 22:26 ` Sripada, Radhakrishna
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=b1b8fffa-06db-1087-a34b-2fa8c39830c4@intel.com \
--to=haridhar.kalvala@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=radhakrishna.sripada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox