From: "Chen, Angus" <angus.chen@intel.com>
To: tejas.upadhyay@intel.com
Cc: andi.shyti@linux.intel.com, angus.chen@intel.com,
intel-gfx@lists.freedesktop.org
Subject: [PATCH v2] drm/i915/mtl: Update workaround 14018778641
Date: Mon, 13 May 2024 13:29:56 +0000 [thread overview]
Message-ID: <20240513132956.73709-1-angus.chen@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6204A1D3BB33FFFBB6BF32E581E52@SJ1PR11MB6204.namprd11.prod.outlook.com>
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);
}
--
2.34.1
next prev parent reply other threads:[~2024-05-13 13:30 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 ` Chen, Angus [this message]
2024-05-14 13:11 ` [PATCH v2] " Chen, Angus
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=20240513132956.73709-1-angus.chen@intel.com \
--to=angus.chen@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tejas.upadhyay@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.