From: "Koppuravuri, Ravi Kishore" <ravi.kishore.koppuravuri@intel.com>
To: <sk.anirban@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<riana.tauro@intel.com>, <karthik.poosa@intel.com>,
<vinay.belgaumkar@intel.com>, <kamil.konieczny@intel.com>
Subject: Re: [PATCH] tests/xe_pmu: Ensure consistent GPU frequency comparison
Date: Thu, 22 May 2025 20:36:58 +0530 [thread overview]
Message-ID: <a1f298cf-c9c9-4b77-8200-2ce82da28410@intel.com> (raw)
In-Reply-To: <20250520171641.2421623-1-sk.anirban@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
Hi,
On 20-05-2025 22:46, sk.anirban@intel.com wrote:
> From: Sk Anirban<sk.anirban@intel.com>
>
> Fetch the minimum frequency only once during GPU frequency restoration.
> This avoids inconsistencies caused by potential changes in the minimum
> frequency between multiple fetches.
>
> Signed-off-by: Sk Anirban<sk.anirban@intel.com>
> ---
> tests/intel/xe_pmu.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tests/intel/xe_pmu.c b/tests/intel/xe_pmu.c
> index c49cceff5..f830c5de8 100644
> --- a/tests/intel/xe_pmu.c
> +++ b/tests/intel/xe_pmu.c
> @@ -390,6 +390,7 @@ static void test_gt_frequency(int fd, struct drm_xe_engine_class_instance *eci)
> uint32_t gt = eci->gt_id;
> uint32_t orig_min = xe_gt_get_freq(fd, eci->gt_id, "min");
> uint32_t orig_max = xe_gt_get_freq(fd, eci->gt_id, "max");
> + uint32_t current_min;
> uint32_t orig_rpe;
> uint32_t vm;
> int pmu_fd[2];
> @@ -440,8 +441,8 @@ static void test_gt_frequency(int fd, struct drm_xe_engine_class_instance *eci)
> */
> igt_assert(xe_gt_set_freq(fd, gt, "min", orig_min) > 0);
> orig_rpe = xe_gt_get_freq(fd, gt, "rpe");
> - igt_assert(xe_gt_get_freq(fd, gt, "min") == orig_min ||
> - xe_gt_get_freq(fd, gt, "min") == orig_rpe);
> + current_min = xe_gt_get_freq(fd, gt, "min");
> + igt_assert(current_min == orig_min || current_min == orig_rpe);
>
> igt_info("Minimum frequency: requested %.1f, actual %.1f\n",
> min[0], min[1]);
It looks good to me.
Reviewed-by: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>
[-- Attachment #2: Type: text/html, Size: 2927 bytes --]
prev parent reply other threads:[~2025-05-23 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 17:16 [PATCH] tests/xe_pmu: Ensure consistent GPU frequency comparison sk.anirban
2025-05-20 20:26 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-05-20 20:36 ` ✓ i915.CI.BAT: " Patchwork
2025-05-21 0:10 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-21 7:41 ` ✗ Xe.CI.Full: " Patchwork
2025-05-23 8:27 ` Anirban, Sk
2025-05-22 12:06 ` [PATCH] " Koppuravuri, Ravi Kishore
2025-05-22 15:06 ` Koppuravuri, Ravi Kishore [this message]
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=a1f298cf-c9c9-4b77-8200-2ce82da28410@intel.com \
--to=ravi.kishore.koppuravuri@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=karthik.poosa@intel.com \
--cc=riana.tauro@intel.com \
--cc=sk.anirban@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 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.