From: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>
To: "Chen, Angus" <angus.chen@intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915/mtl: Update workaround 14018778641
Date: Wed, 8 May 2024 14:17:18 +0000 [thread overview]
Message-ID: <SJ1PR11MB6204A1D3BB33FFFBB6BF32E581E52@SJ1PR11MB6204.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c4e0d0c2-e22d-4cef-b6ba-d11970451ed9@intel.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Chen,
> Angus
> Sent: Tuesday, April 30, 2024 4:50 PM
> To: Andi Shyti <andi.shyti@linux.intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [PATCH] drm/i915/mtl: Update workaround 14018778641
>
> The original workaround was from
> https://patchwork.freedesktop.org/patch/533574/
> Then, we don't apply WA to VDBOX, VEBOX and RENDER engine with the
> following patch
> https://patchwork.freedesktop.org/patch/543117/?series=119517&rev=1
> But now we need this WA to cover VDBOX.
>
> On 4/29/2024 5:53 PM, Andi Shyti wrote:
> > Hi Angus,
> >
> > ...
> >
> >> @@ -1586,6 +1586,8 @@ 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_write_or(wal, XELPMP_VDBX_MOD_CTRL, FORCE_MISS_FTLB);
> > Can you please add the reference of the workaround in a comment here?
As far as I know media team confirmed that there is no perf impact and this WA can be removed. As Andi said, reference would be help here.
Thanks,
Tejas
> >
> > Thanks,
> > Andi
> >
> >> +
next prev parent reply other threads:[~2024-05-08 14:17 UTC|newest]
Thread overview: 16+ 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 [this message]
2024-05-13 13:29 ` [PATCH v2] " Chen, Angus
2024-05-14 13:11 ` 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
-- strict thread matches above, loose matches on Subject: below --
2024-02-22 13:57 [PATCH] drm/i915/mtl: Update workaround 14018778641 Tejas Upadhyay
2024-02-22 21:45 ` 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=SJ1PR11MB6204A1D3BB33FFFBB6BF32E581E52@SJ1PR11MB6204.namprd11.prod.outlook.com \
--to=tejas.upadhyay@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=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 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.