From: Raag Jadav <raag.jadav@intel.com>
To: Sk Anirban <sk.anirban@intel.com>
Cc: igt-dev@lists.freedesktop.org, anshuman.gupta@intel.com,
badal.nilawar@intel.com, riana.tauro@intel.com,
karthik.poosa@intel.com, soham.purkait@intel.com,
mallesh.koujalagi@intel.com
Subject: Re: [PATCH v3 1/2] tests/intel/xe_gt_freq: Modify test to support new throttle reasons sysfs
Date: Thu, 11 Dec 2025 14:29:09 +0100 [thread overview]
Message-ID: <aTrHJXa0wT4kNTKd@black.igk.intel.com> (raw)
In-Reply-To: <aTqRG7VWGnsJTdkh@black.igk.intel.com>
On Thu, Dec 11, 2025 at 10:38:40AM +0100, Raag Jadav wrote:
> On Wed, Dec 10, 2025 at 10:49:24AM +0530, Sk Anirban wrote:
> > Change throttle_basic_api to read the new atomic reasons attribute
> > instead of checking status and individual reason files separately.
> > This validates the kernel's TOCTOU-free throttling interface.
> >
> > v2: Update buffer size (Raag)
> > Cosmetic changes (Raag)
> > v3: Update fd name (Raag)
> > Modify output (Raag)
> >
> > Signed-off-by: Sk Anirban <sk.anirban@intel.com>
>
> Reviewed-by: Raag Jadav <raag.jadav@intel.com>
On second thought, I'm wondering if we can redesign the test as below.
1. Start throttle test.
2. Wait for gt to idle.
3. Check throttle reasons.
4. Assert if reason is not 'none'.
With this we can potentially catch pcode misbehaviour.
Thoughts?
Raag
next prev parent reply other threads:[~2025-12-11 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 5:19 [PATCH v3 0/2] tests/intel/xe_gt_freq: Modify test to support new throttle reasons sysfs Sk Anirban
2025-12-10 5:19 ` [PATCH v3 1/2] " Sk Anirban
2025-12-11 9:38 ` Raag Jadav
2025-12-11 13:29 ` Raag Jadav [this message]
2025-12-10 5:19 ` [PATCH v3 2/2] HAX: Add throttle_basic_api test to fast feedback list Sk Anirban
2025-12-10 10:18 ` ✓ Xe.CI.BAT: success for tests/intel/xe_gt_freq: Modify test to support new throttle reasons sysfs (rev4) Patchwork
2025-12-10 11:13 ` ✓ i915.CI.BAT: " Patchwork
2025-12-10 13:52 ` ✗ i915.CI.Full: failure " Patchwork
2025-12-10 14:04 ` ✗ Xe.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-12-09 11:11 [PATCH v3 0/2] tests/intel/xe_gt_freq: Modify test to support new throttle reasons sysfs Sk Anirban
2025-12-09 11:11 ` [PATCH v3 1/2] " Sk Anirban
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=aTrHJXa0wT4kNTKd@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=riana.tauro@intel.com \
--cc=sk.anirban@intel.com \
--cc=soham.purkait@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.