From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] test/intel/xe_guc_pc: Fix freq_low_max test
Date: Thu, 14 Dec 2023 09:50:01 -0800 [thread overview]
Message-ID: <3bb30a92-ba3d-49fa-9bcc-18d3ff09cf87@intel.com> (raw)
In-Reply-To: <20231124102946.2650848-3-badal.nilawar@intel.com>
On 11/24/2023 2:29 AM, Badal Nilawar wrote:
> freq_low_max test is intended to validate GuC PC (SLPC) behaviour
> when max freq set to less than min freq. As workloads are not being
> run validating cur freq is enough.
>
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
> ---
> tests/intel/xe_guc_pc.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tests/intel/xe_guc_pc.c b/tests/intel/xe_guc_pc.c
> index c23017501..70548ba0e 100644
> --- a/tests/intel/xe_guc_pc.c
> +++ b/tests/intel/xe_guc_pc.c
> @@ -220,7 +220,6 @@ static void test_freq_low_max(int fd, int gt_id)
> igt_assert(set_freq(fd, gt_id, "max", rpn) > 0);
> usleep(ACT_FREQ_LATENCY_US);
> igt_assert(get_freq(fd, gt_id, "cur") == rpe);
> - igt_assert(get_freq(fd, gt_id, "act") == rpe);
might be worth keeping this check with if (!in_rc6()). We hardly check
for actual frequency, this will be a good way to ensure we can even get
efficient freq.
Thanks,
Vinay.
> }
>
> /**
next prev parent reply other threads:[~2023-12-14 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:29 [igt-dev] [PATCH i-g-t 0/2] Couple of fixes to guc_pc tests Badal Nilawar
2023-11-24 10:29 ` [igt-dev] [PATCH i-g-t 1/2] test/intel/xe_guc_pc: Skip freq_*_idle tests on PVC Badal Nilawar
2023-11-24 11:21 ` Ch, Sai Gowtham
2023-11-24 10:29 ` [igt-dev] [PATCH i-g-t 2/2] test/intel/xe_guc_pc: Fix freq_low_max test Badal Nilawar
2023-12-14 17:50 ` Belgaumkar, Vinay [this message]
2023-11-24 13:06 ` [igt-dev] ✗ Fi.CI.BAT: failure for Couple of fixes to guc_pc tests Patchwork
2023-11-24 14:46 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
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=3bb30a92-ba3d-49fa-9bcc-18d3ff09cf87@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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