From: Gustavo Sousa <gustavo.sousa@intel.com>
To: "Vivekanandan,
Balasubramani" <balasubramani.vivekanandan@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: "Tangudu, Tilak Tirumalesh" <tilak.tirumalesh.tangudu@intel.com>
Subject: Re: [PATCH v2 04/10] drm/xe: Factor out {min,max}_idledly_ps in adjust_idledly()
Date: Tue, 3 Nov 2026 11:07:32 -0300 [thread overview]
Message-ID: <875wyeqa8r.fsf@intel.com> (raw)
In-Reply-To: <auiFQzhrWnqYnoNE@bvivekan-mobl1>
"Vivekanandan, Balasubramani" <balasubramani.vivekanandan@intel.com>
writes:
> On 30.10.2026 19:57, Gustavo Sousa wrote:
>> The function adjust_idledly() currently does the following adjustments
>> to the IDLEDLY register:
>>
>> - Wa_14025941587 defines a minimum value for the idle delay.
>>
>> - Wa_16023105232 defines a maximum value for the idle delay and also
>> unsets INHIBIT_SWITCH_UNTIL_PREEMPTED.
>>
>> We have an upcoming workaround that will also define a minimum idle
>> delay.
>>
>> Let's reorganize the logic in adjust_idledly() in a way to make it
>> easier to reason about and also easier to extend.
>>
>> Do that by having the workaround-specific logic only responsible for
>> defining min_idledly_ps or max_idledly_ps, and then keeping the logic of
>> how to apply them to the register field (with the right rounding up or
>> down) separate.
>>
>> This separation drops the helper function idledly_floor_ticks(), the
>> clamped_below_maxcnt variable, and the extra quantization check,
>> arguably making the code easier to follow.
>>
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_hw_engine.c | 100 ++++++++++++++++----------------------
>> 1 file changed, 41 insertions(+), 59 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c b/drivers/gpu/drm/xe/xe_hw_engine.c
>> index eb99284af3cc..01a7baf061eb 100644
>> --- a/drivers/gpu/drm/xe/xe_hw_engine.c
>> +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
>> @@ -596,99 +596,81 @@ static void hw_engine_init_early(struct xe_gt *gt, struct xe_hw_engine *hwe,
>> xe_reg_whitelist_process_engine(hwe);
>> }
>>
>> -static u32 idledly_floor_ticks(u64 idledly_ps, u64 idledly_units_ps)
>> -{
>> - return DIV_ROUND_DOWN_ULL(idledly_ps, idledly_units_ps);
>> -}
>> -
>> static void adjust_idledly(struct xe_hw_engine *hwe)
>> {
>> struct xe_gt *gt = hwe->gt;
>> - u32 idledly_reg_val, maxcnt_reg_val;
>> + u32 idledly_reg_val;
>> + u32 idledly;
>> u64 idledly_units_ps = 8 * gt->info.timestamp_base;
>> - u64 maxcnt_units_ps = 640000;
>> u64 idledly_ps, idledly_hw_ps;
>> - u64 maxcnt_ps;
>> + u64 min_idledly_ps = 0;
>> + u64 max_idledly_ps = -1;
>> bool inhibit_switch = false;
>> bool wa_applied = false;
>> - bool clamped_below_maxcnt = false;
>>
>> if (IS_SRIOV_VF(gt_to_xe(gt)))
>> return;
>>
>> if (XE_GT_WA(gt, 16023105232) || XE_GT_WA(gt, 14025941587)) {
>> - u32 mincnt_idledly_ps = 5000000;
>> -
>> /* xe_gt_clock_init() warns and zeroes timestamp_base on unknown crystal clock. */
>> if (!idledly_units_ps)
>> return;
>>
>> idledly_reg_val = xe_mmio_read32(>->mmio, RING_IDLEDLY(hwe->mmio_base));
>> inhibit_switch = idledly_reg_val & INHIBIT_SWITCH_UNTIL_PREEMPTED;
>> - idledly_ps = REG_FIELD_GET(IDLE_DELAY, idledly_reg_val) * idledly_units_ps;
>> + idledly = REG_FIELD_GET(IDLE_DELAY, idledly_reg_val);
>> + idledly_ps = idledly * idledly_units_ps;
>> idledly_hw_ps = idledly_ps;
>>
>> - maxcnt_reg_val = xe_mmio_read32(>->mmio, RING_PWRCTX_MAXCNT(hwe->mmio_base));
>> - maxcnt_ps = REG_FIELD_GET(IDLE_WAIT_TIME, maxcnt_reg_val) * maxcnt_units_ps;
>> -
>> - /*
>> - * Wa_14025941587 is applied before Wa_16023105232, which takes
>> - * priority if the two ever conflict (not expected in practice).
>> - */
>> - if (XE_GT_WA(gt, 14025941587) &&
>> - idledly_ps < mincnt_idledly_ps) {
>> - idledly_ps = mincnt_idledly_ps;
>> - wa_applied = true;
>> - }
>> + if (XE_GT_WA(gt, 14025941587))
>> + min_idledly_ps = max(min_idledly_ps, 5000000);
>
> There is no need of check, we can directly assign 5000000.
You are right, but still I would prefer this approach as a standard way
of setting min_idledly_ps. It makes it easier to add new minimum values
before or after this "if" statement. This also makes it easy to
move/drop this statement in the future if needed.
--
Gustavo Sousa
>
> + Tilak
>
> Regards,
> Bala
>
>>
>> if (XE_GT_WA(gt, 16023105232)) {
>> + u64 maxcnt_units_ps = 640000;
>> + u32 maxcnt = xe_mmio_read32(>->mmio, RING_PWRCTX_MAXCNT(hwe->mmio_base));
>> +
>> + max_idledly_ps = min_t(u64,
>> + max_idledly_ps,
>> + REG_FIELD_GET(IDLE_WAIT_TIME, maxcnt) * maxcnt_units_ps);
>> +
>> /* Clear the inhibit switch without disturbing a valid delay. */
>> if (inhibit_switch) {
>> idledly_reg_val &= ~INHIBIT_SWITCH_UNTIL_PREEMPTED;
>> wa_applied = true;
>> }
>> + }
>>
>> - /* Warn only on the value read from hardware. */
>> - xe_gt_WARN_ON(gt, idledly_hw_ps >= maxcnt_ps);
>> + /*
>> + * min_idledly_ps is applied before max_idledly_ps, which takes
>> + * priority if the two ever conflict (not expected in practice).
>> + */
>> + if (idledly_ps < min_idledly_ps) {
>> + idledly = DIV_ROUND_UP_ULL(min_idledly_ps, idledly_units_ps);
>> + idledly_ps = idledly * idledly_units_ps;
>> + wa_applied = true;
>> + }
>>
>> - if (idledly_ps >= maxcnt_ps) {
>> - /* maxcnt may be 0 if IDLE_WAIT_TIME is unprogrammed. */
>> - idledly_ps = maxcnt_ps ? maxcnt_ps - 1 : 0;
>> - clamped_below_maxcnt = true;
>> - wa_applied = true;
>> + if (idledly_ps >= max_idledly_ps) {
>> + if (max_idledly_ps) {
>> + idledly = DIV_ROUND_DOWN_ULL(max_idledly_ps - 1, idledly_units_ps);
>> + idledly_ps = idledly * idledly_units_ps;
>> + } else {
>> + idledly = 0;
>> + idledly_ps = 0;
>> }
>> +
>> + wa_applied = true;
>> }
>>
>> - if (wa_applied) {
>> - u32 idledly_ticks;
>> -
>> - /*
>> - * Wa_16023105232 requires idledly < maxcnt, so floor
>> - * that clamp; otherwise round up to guarantee the
>> - * Wa_14025941587 minimum survives tick quantization.
>> - */
>> - if (clamped_below_maxcnt)
>> - idledly_ticks = idledly_floor_ticks(idledly_ps, idledly_units_ps);
>> - else
>> - idledly_ticks = DIV_ROUND_UP_ULL(idledly_ps, idledly_units_ps);
>> -
>> - /*
>> - * Tick quantization can still push the rounded-up value
>> - * to/above maxcnt; re-floor here so Wa_16023105232 keeps
>> - * priority even in that case.
>> - */
>> - if (!clamped_below_maxcnt && XE_GT_WA(gt, 16023105232) &&
>> - idledly_ticks * idledly_units_ps >= maxcnt_ps) {
>> - xe_gt_dbg(gt, "idledly %s: %u ticks would exceed maxcnt=%llups, so flooring\n",
>> - hwe->name, idledly_ticks, maxcnt_ps);
>> - idledly_ps = maxcnt_ps ? maxcnt_ps - 1 : 0;
>> - idledly_ticks = idledly_floor_ticks(idledly_ps, idledly_units_ps);
>> - }
>> + /* Warn only if the value read from *hardware* exceeds the maximum. */
>> + xe_gt_WARN_ON(gt, idledly_hw_ps >= max_idledly_ps);
>>
>> + if (wa_applied) {
>> idledly_reg_val &= ~IDLE_DELAY;
>> - idledly_reg_val |= REG_FIELD_PREP(IDLE_DELAY, idledly_ticks);
>> - xe_gt_dbg(gt, "idledly %s: set %llups max=%llups inh=%u ts=%ups\n",
>> - hwe->name, idledly_ps, maxcnt_ps,
>> + idledly_reg_val |= REG_FIELD_PREP(IDLE_DELAY, idledly);
>> +
>> + xe_gt_dbg(gt, "idledly %s: set %llups min=%llups max=%llups inh=%u ts=%ups\n",
>> + hwe->name, idledly_ps, min_idledly_ps, max_idledly_ps,
>> !!inhibit_switch, gt->info.timestamp_base);
>> xe_mmio_write32(>->mmio,
>> RING_IDLEDLY(hwe->mmio_base),
>>
>> --
>> 2.56.0
>>
next prev parent reply other threads:[~2026-11-03 14:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 22:57 [PATCH v2 00/10] drm/xe: Clean up adjust_idledly() and implement Wa_16031259911 Gustavo Sousa
2026-10-30 22:57 ` [PATCH v2 01/10] drm/xe: Bail from adjust_idledly() if in VF mode Gustavo Sousa
2026-10-30 22:57 ` [PATCH v2 02/10] drm/xe: Sync Wa_16023105232 in xe_was to match OOB rule Gustavo Sousa
2026-10-30 22:57 ` [PATCH v2 03/10] drm/xe: Use picosecond as common unit in adjust_idledly() Gustavo Sousa
2026-11-02 18:54 ` Matt Atwood
2026-10-30 22:57 ` [PATCH v2 04/10] drm/xe: Factor out {min,max}_idledly_ps " Gustavo Sousa
2026-11-02 12:42 ` Vivekanandan, Balasubramani
2026-11-03 14:07 ` Gustavo Sousa [this message]
2026-10-30 22:57 ` [PATCH v2 05/10] drm/xe: Bail from adjust_idledly() if no applicable workaround Gustavo Sousa
2026-11-02 12:54 ` Vivekanandan, Balasubramani
2026-11-03 14:20 ` Gustavo Sousa
2026-11-04 17:06 ` Matt Atwood
2026-10-30 22:57 ` [PATCH v2 06/10] drm/xe: Drop early and redundant workaround checks in adjust_idledly() Gustavo Sousa
2026-11-02 12:58 ` Vivekanandan, Balasubramani
2026-10-30 22:57 ` [PATCH v2 07/10] drm/xe: Replace MAXCNT comment with a comment on adjust_idledly() Gustavo Sousa
2026-11-02 18:48 ` Matt Atwood
2026-10-30 22:57 ` [PATCH v2 08/10] drm/xe/guc: Increment regset size for Wa_1607983814 inside hwe loop Gustavo Sousa
2026-10-30 22:57 ` [PATCH v2 09/10] drm/xe/guc: Increment regset size for RING_IDLEDLY workarounds Gustavo Sousa
2026-10-30 22:57 ` [PATCH v2 10/10] drm/xe: Implement Wa_16031259911 Gustavo Sousa
2026-10-30 23:15 ` ✗ CI.checkpatch: warning for drm/xe: Clean up adjust_idledly() and implement Wa_16031259911 (rev2) Patchwork
2026-10-30 23:17 ` ✓ CI.KUnit: success " Patchwork
2026-10-30 23:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-31 19:00 ` ✓ Xe.CI.FULL: " Patchwork
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=875wyeqa8r.fsf@intel.com \
--to=gustavo.sousa@intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tilak.tirumalesh.tangudu@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