From: "Chauhan, Shekhar" <shekhar.chauhan@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
<intel-gfx@lists.freedesktop.org>, <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Add Wa_18028616096
Date: Fri, 22 Sep 2023 09:34:36 +0530 [thread overview]
Message-ID: <5e2c29a6-083e-4f84-932e-a14fed53086c@intel.com> (raw)
In-Reply-To: <169533011276.1903.10121233791745587247@gjsousa-mobl2>
[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]
Quoting Gustavo Sousa:
On 9/22/2023 02:31, Gustavo Sousa wrote:
> Quoting Shekhar Chauhan (2023-09-21 11:30:28-03:00)
>> Drop UGM per set fragment threshold to 3
>>
>> BSpec: 54833
>> Signed-off-by: Shekhar Chauhan<shekhar.chauhan@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 +
>> drivers/gpu/drm/i915/gt/intel_workarounds.c | 3 +++
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> index a00ff51c681d..431c575c532b 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> @@ -1230,6 +1230,7 @@
>> #define DISABLE_D8_D16_COASLESCE REG_BIT(30)
>> #define FORCE_1_SUB_MESSAGE_PER_FRAGMENT REG_BIT(15)
>> #define LSC_CHICKEN_BIT_0_UDW MCR_REG(0xe7c8 + 4)
>> +#define UGM_FRAGMENT_THRESHOLD_TO_3 REG_BIT(58 - 32)
>> #define DIS_CHAIN_2XSIMD8 REG_BIT(55 - 32)
>> #define FORCE_SLM_FENCE_SCOPE_TO_TILE REG_BIT(42 - 32)
>> #define FORCE_UGM_FENCE_SCOPE_TO_TILE REG_BIT(41 - 32)
>> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> index 660d4f358eab..992041e3776c 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> @@ -2914,6 +2914,9 @@ general_render_compute_wa_init(struct intel_engine_cs *engine, struct i915_wa_li
>> * Wa_22015475538:dg2
>> */
>> wa_mcr_write_or(wal, LSC_CHICKEN_BIT_0_UDW, DIS_CHAIN_2XSIMD8);
>> +
>> + /* Wa_18028616096:dg2 */
> This is not a blocker, but I would prefer to remove the ":dg2" suffix.
>
> There was an effort to remove them from our driver[1], but it kinda of
> stalled. I myself agree that we would be better off without them.
>
> [1]https://lore.kernel.org/all/20221222082557.1364711-1-lucas.demarchi@intel.com
Ack'ed in the new version.
>
>> + wa_mcr_write_or(wal, LSC_CHICKEN_BIT_0_UDW, UGM_FRAGMENT_THRESHOLD_TO_3);
> This workaround applies to (i) DG2 G10 from stepping C0 to forever and
> (ii) any stepping of DG2 G12. Here you are applying this workaround to
> any variant of DG2.
>
> It should be moved out of this "if" statement and rather be guarded by
> something like:
>
> if ((IS_DG2_G10(i915) && IS_GRAPHICS_STEP(i915, STEP_C0, STEP_FOREVER)) ||
> IS_DG2_G12(i915))
>
> Note that we are there is still a pending decision for G11, so we may
> need to update this in the future.
I believe we're only supporting production steppings for DG2,
henceforth, not really interacting with the "older" steppings.
Please have a look:
https://lore.kernel.org/intel-gfx/20230816214201.534095-7-matthew.d.roper@intel.com/
Although, I could be wrong, if I am, I'll send in another version,
modifying the patch as you've suggested.
> --
> Gustavo Sousa
>
>> }
>>
>> if (IS_DG2_G11(i915)) {
>> --
>> 2.34.1
>>
--
-shekhar
[-- Attachment #2: Type: text/html, Size: 40158 bytes --]
next prev parent reply other threads:[~2023-09-22 4:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 14:30 [Intel-gfx] [PATCH] drm/i915: Add Wa_18028616096 Shekhar Chauhan
2023-09-21 21:01 ` Gustavo Sousa
2023-09-22 4:04 ` Chauhan, Shekhar [this message]
2023-09-22 12:17 ` Gustavo Sousa
2023-09-22 0:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Add Wa_18028616096 (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 3:50 [Intel-gfx] [PATCH] drm/i915: Add Wa_18028616096 Shekhar Chauhan
2023-09-21 4:27 Shekhar Chauhan
2023-09-21 7:17 ` kernel test robot
2023-09-21 8:20 ` kernel test robot
2023-09-20 4:05 Shekhar Chauhan
2023-09-20 6:42 ` kernel test robot
2023-09-20 13:42 ` Gustavo Sousa
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=5e2c29a6-083e-4f84-932e-a14fed53086c@intel.com \
--to=shekhar.chauhan@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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