From: "Chen, Angus" <angus.chen@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915/mtl: Update workaround 14018778641
Date: Tue, 14 May 2024 21:11:18 +0800 [thread overview]
Message-ID: <b34b1cf4-b07f-4937-90ec-918fd3819209@intel.com> (raw)
In-Reply-To: <20240513132956.73709-1-angus.chen@intel.com>
Please ignore this patch. (Wrong branch)
On 5/13/2024 9:29 PM, Chen, Angus wrote:
> From: Angus Chen <angus.chen@intel.com>
>
> Applying it to VDBOX after recent performance data on MTL
>
> Signed-off-by: Angus Chen <angus.chen@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> index f3332bc55b8f..8432fb4fd28d 100644
> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> @@ -1695,6 +1695,9 @@ xelpmp_gt_workarounds_init(struct intel_gt *gt, struct i915_wa_list *wal)
> */
> wa_write_or(wal, XELPMP_GSC_MOD_CTRL, FORCE_MISS_FTLB);
>
> + /* Wa_14018778641 */
> + wa_write_or(wal, XELPMP_VDBX_MOD_CTRL, FORCE_MISS_FTLB);
> +
> debug_dump_steering(gt);
> }
>
next prev parent reply other threads:[~2024-05-14 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:36 [PATCH] drm/i915/mtl: Update workaround 14018778641 Chen, Angus
2024-04-26 8:38 ` ✗ Fi.CI.BAT: failure for drm/i915/mtl: Update workaround 14018778641 (rev4) Patchwork
2024-04-29 9:53 ` [PATCH] drm/i915/mtl: Update workaround 14018778641 Andi Shyti
2024-04-30 11:20 ` Chen, Angus
2024-05-08 14:17 ` Upadhyay, Tejas
2024-05-13 13:29 ` [PATCH v2] " Chen, Angus
2024-05-14 13:11 ` Chen, Angus [this message]
2024-05-13 14:19 ` Chen, Angus
2024-05-23 22:31 ` Andi Shyti
2024-05-23 23:24 ` Matt Roper
2024-05-24 11:26 ` Andi Shyti
2024-05-24 16:00 ` Matt Roper
2024-05-24 17:33 ` [PATCH v3] drm/i915/mtl: Update workaround 14018575942 Chen, Angus
2024-05-27 10:38 ` Andi Shyti
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=b34b1cf4-b07f-4937-90ec-918fd3819209@intel.com \
--to=angus.chen@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).