From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Sk Anirban <sk.anirban@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <riana.tauro@intel.com>,
<karthik.poosa@intel.com>, <raag.jadav@intel.com>,
<soham.purkait@intel.com>, <mallesh.koujalagi@intel.com>,
<vinay.belgaumkar@intel.com>
Subject: Re: [PATCH 1/2] tests/intel/xe_pmu: Fix frequency assertion when RPe raises min frequency
Date: Fri, 14 Nov 2025 18:40:08 +0530 [thread overview]
Message-ID: <0dee33e5-0c36-4beb-a98f-00707da65ee5@intel.com> (raw)
In-Reply-To: <20251030192627.3810994-3-sk.anirban@intel.com>
On 31-10-2025 00:56, Sk Anirban wrote:
> While running workloads, RPe may dynamically raise the minimum frequency
> above the original value. To balance this, set the minimum frequency to
> original minimum.
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5841
> Suggested-by: Badal Nilawar <badal.nilawar@intel.com>
> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
> ---
> tests/intel/xe_pmu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/intel/xe_pmu.c b/tests/intel/xe_pmu.c
> index 9525655ba..1a5b17de0 100644
> --- a/tests/intel/xe_pmu.c
> +++ b/tests/intel/xe_pmu.c
> @@ -912,6 +912,7 @@ static void test_gt_frequency(int fd, struct drm_xe_engine_class_instance *eci)
> /*
> * Set GPU to min frequency and read PMU counters.
> */
> + igt_assert(xe_gt_set_freq(fd, gt, "min", orig_min) > 0);
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
> igt_assert(xe_gt_set_freq(fd, gt, "max", orig_min) > 0);
> igt_assert(xe_gt_get_freq(fd, gt, "max") == orig_min);
>
next prev parent reply other threads:[~2025-11-14 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 19:26 [PATCH 1/2] tests/intel/xe_pmu: Fix frequency assertion when RPe raises min frequency Sk Anirban
2025-10-30 19:26 ` [PATCH 2/2] HAX: Add gt-frequency test to fast feedback list Sk Anirban
2025-10-30 23:54 ` ✓ i915.CI.BAT: success for series starting with [1/2] tests/intel/xe_pmu: Fix frequency assertion when RPe raises min frequency Patchwork
2025-10-31 0:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-31 9:20 ` ✓ Xe.CI.Full: " Patchwork
2025-10-31 12:47 ` ✗ i915.CI.Full: failure " Patchwork
2025-11-14 13:10 ` Nilawar, Badal [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-16 10:29 [PATCH 0/2] " Sk Anirban
2025-10-16 10:29 ` [PATCH 1/2] tests/intel/xe_pmu: " 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=0dee33e5-0c36-4beb-a98f-00707da65ee5@intel.com \
--to=badal.nilawar@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=sk.anirban@intel.com \
--cc=soham.purkait@intel.com \
--cc=vinay.belgaumkar@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;
as well as URLs for NNTP newsgroup(s).