From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v5] drm/xe/gt_throttle: Avoid TOCTOU when monitoring reasons
Date: Wed, 5 Nov 2025 14:27:11 +0100 [thread overview]
Message-ID: <aQtQr4ks-Nxi2z1W@black.igk.intel.com> (raw)
In-Reply-To: <20251104-gt-throttle-cri-v5-1-4948b060bbfd@intel.com>
On Tue, Nov 04, 2025 at 02:20:51PM -0800, Lucas De Marchi wrote:
> It's currently not possible to safely monitor if there's throttling
> happening and what are the reasons. The approach of reading the status
> and then reading the reasons is not reliable as by the time sysadmin
> reads the reason, the throttling could not be happening anymore.
>
> Previous tentative to fix that[1] was breaking the ABI and potentially
> sysadmin's scripts. This takes a different approach of adding and
> documenting the additional attribute. It's still valuable, though
> redundant, to provide the simpler 0/1 interface.
>
> In order to avoid userspace knowledge on the bitmask meaning and to be
> able to maintain the kernel side in sync with possible changes in
> future, just walk the attribute group and check what are the masks that
> match the value read.
>
> [1] https://lore.kernel.org/intel-xe/20241025092238.167042-1-raag.jadav@intel.com/
...
> +static const struct attribute_group *get_platform_throttle_group(struct xe_device *xe);
> +
> +static ssize_t reasons_show(struct kobject *kobj,
> + struct kobj_attribute *attr, char *buff)
> +{
> + struct xe_gt *gt = throttle_to_gt(kobj);
> + struct xe_device *xe = gt_to_xe(gt);
> + const struct attribute_group *group;
> + struct attribute **pother;
> + ssize_t ret = 0;
> + u32 reasons;
> +
> + reasons = xe_gt_throttle_get_limit_reasons(gt);
> + if (!reasons)
> + goto ret_none;
> +
> + group = get_platform_throttle_group(xe);
> + for (pother = group->attrs; *pother; pother++) {
> + struct kobj_attribute *kattr = container_of(*pother, struct kobj_attribute, attr);
> + struct throttle_attribute *other_ta = kobj_attribute_to_throttle(kattr);
> +
> + if (other_ta->mask != U32_MAX && reasons & other_ta->mask)
> + ret += sysfs_emit_at(buff, ret, "%s ", (*pother)->name);
> + }
> +
> + if (drm_WARN_ONCE(&xe->drm, !ret, "Unknown reason: %#x\n", reasons))
Nit: I know we're masking it but I'm a bit more used to the full format for
register values, i.e. 0x%08x
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
> + goto ret_none;
> +
> + /* Drop extra space from last iteration above */
> + ret--;
> + ret += sysfs_emit_at(buff, ret, "\n");
> +
> + return ret;
> +
> +ret_none:
> + return sysfs_emit(buff, "none\n");
> +}
> +
> #define THROTTLE_ATTR_RO(name, _mask) \
> struct throttle_attribute attr_##name = { \
> .attr = __ATTR(name, 0444, reason_show, NULL), \
> .mask = _mask, \
> }
>
> +#define THROTTLE_ATTR_RO_FUNC(name, _mask, _show) \
> + struct throttle_attribute attr_##name = { \
> + .attr = __ATTR(name, 0444, _show, NULL), \
> + .mask = _mask, \
> + }
> +
> +static THROTTLE_ATTR_RO_FUNC(reasons, 0, reasons_show);
> static THROTTLE_ATTR_RO(status, U32_MAX);
> static THROTTLE_ATTR_RO(reason_pl1, POWER_LIMIT_1_MASK);
> static THROTTLE_ATTR_RO(reason_pl2, POWER_LIMIT_2_MASK);
> @@ -128,6 +180,7 @@ static THROTTLE_ATTR_RO(reason_vr_thermalert, VR_THERMALERT_MASK);
> static THROTTLE_ATTR_RO(reason_vr_tdc, VR_TDC_MASK);
>
> static struct attribute *throttle_attrs[] = {
> + &attr_reasons.attr.attr,
> &attr_status.attr.attr,
> &attr_reason_pl1.attr.attr,
> &attr_reason_pl2.attr.attr,
> @@ -153,6 +206,7 @@ static THROTTLE_ATTR_RO(reason_psys_crit, PSYS_CRIT_MASK);
>
> static struct attribute *cri_throttle_attrs[] = {
> /* Common */
> + &attr_reasons.attr.attr,
> &attr_status.attr.attr,
> &attr_reason_pl1.attr.attr,
> &attr_reason_pl2.attr.attr,
>
>
>
next prev parent reply other threads:[~2025-11-05 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 22:20 [PATCH v5] drm/xe/gt_throttle: Avoid TOCTOU when monitoring reasons Lucas De Marchi
2025-11-05 3:59 ` ✗ CI.checkpatch: warning for drm/xe/gt_throttle: Avoid TOCTOU when monitoring reasons (rev2) Patchwork
2025-11-05 4:00 ` ✓ CI.KUnit: success " Patchwork
2025-11-05 4:55 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-05 11:23 ` ✓ Xe.CI.Full: " Patchwork
2025-11-05 13:27 ` Raag Jadav [this message]
2025-11-05 13:35 ` [PATCH v5] drm/xe/gt_throttle: Avoid TOCTOU when monitoring reasons Raag Jadav
2025-11-05 17:05 ` Lucas De Marchi
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=aQtQr4ks-Nxi2z1W@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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