All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH] tests/xe_pmu: Adjust assertion to account for potential RPe adjustments by GuC
Date: Wed, 7 May 2025 16:21:21 +0530	[thread overview]
Message-ID: <dd4fc81e-7b29-4bd3-b135-bc7e30861107@intel.com> (raw)
In-Reply-To: <20250506150617.1961348-1-sk.anirban@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

Hi,

On 06-05-2025 20:36, sk.anirban@intel.com wrote:
> From: Sk Anirban<sk.anirban@intel.com>
>
> In scenarios where the GuC adjusts the RPe, the minimum frequency may align
> with the adjusted RPe frequency. The assertion has been updated to account
> for this scenario.
>
> Signed-off-by: Sk Anirban<sk.anirban@intel.com>
> ---
>   tests/intel/xe_pmu.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tests/intel/xe_pmu.c b/tests/intel/xe_pmu.c
> index 094dc0c6c..2e29a4056 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 orig_rpe;
>   	uint32_t vm;
>   	int pmu_fd[2];
>   
> @@ -438,7 +439,9 @@ static void test_gt_frequency(int fd, struct drm_xe_engine_class_instance *eci)
>   	 * Restore min/max.
>   	 */
>   	igt_assert(xe_gt_set_freq(fd, gt, "min", orig_min) > 0);
> -	igt_assert(xe_gt_get_freq(fd, gt, "min") == orig_min);
> +	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);
>   
>   	igt_info("Minimum frequency: requested %.1f, actual %.1f\n",
>   		 min[0], min[1]);

Looks good to me.

Reviewed-by: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>

[-- Attachment #2: Type: text/html, Size: 2813 bytes --]

  parent reply	other threads:[~2025-05-08 10:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 15:06 [PATCH] tests/xe_pmu: Adjust assertion to account for potential RPe adjustments by GuC sk.anirban
2025-05-06 18:16 ` ✓ i915.CI.BAT: success for " Patchwork
2025-05-06 18:24 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-06 20:02 ` ✓ i915.CI.Full: " Patchwork
2025-05-06 23:30 ` ✓ Xe.CI.Full: " Patchwork
2025-05-07 10:51 ` Koppuravuri, Ravi Kishore [this message]
2025-05-08  3:56 ` [PATCH] " Koppuravuri, Ravi Kishore
2025-05-08 10:20 ` Koppuravuri, Ravi Kishore

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=dd4fc81e-7b29-4bd3-b135-bc7e30861107@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=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.