From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>, <vinay.belgaumkar@intel.com>
Subject: Re: [PATCH i-g-t 2/2] "tests/intel/xe_gt_freq: Fix freq_low_max test
Date: Fri, 14 Jun 2024 19:49:57 +0530 [thread overview]
Message-ID: <ce394992-ca36-4f9c-8cbd-6953825e4286@intel.com> (raw)
In-Reply-To: <20240614133722.6ok4fvliugt5pd3b@kamilkon-DESK.igk.intel.com>
On 14-06-2024 19:07, Kamil Konieczny wrote:
> Hi Badal,
> On 2024-06-14 at 15:37:12 +0530, Badal Nilawar wrote:
>> Intention of freq_low_max is to validate GuC PC flow when max freq set
>> to less than min freq. Validating cur freq is enough as workloads are
>> not being run.
>>
>> Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
>
> Instead of revert and fixing revert, please send one patch
> and add there which one did you fixed.
Sure, will send one patch with fixed tag
>
>> ---
>> tests/intel/xe_gt_freq.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/tests/intel/xe_gt_freq.c b/tests/intel/xe_gt_freq.c
>> index 24333612b..b3562181d 100644
>> --- a/tests/intel/xe_gt_freq.c
>> +++ b/tests/intel/xe_gt_freq.c
>> @@ -277,7 +277,6 @@ static void test_freq_low_max(int fd, int gt_id)
>> rpe = get_freq(fd, gt_id, "rpe");
>>
>> igt_assert(get_freq(fd, gt_id, "cur") == rpe);
>> - igt_assert(get_freq(fd, gt_id, "act") == rpe);
>
> Why ot writing comment here why "act" frequency is not checked?
Sure, will add comment.
Thanks,
Badal
>
> Regards,
> Kamil
>
>> }
>>
>> /**
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2024-06-14 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 10:07 [PATCH i-g-t 0/2] Fix freq_low_max test Badal Nilawar
2024-06-14 10:07 ` [PATCH i-g-t 1/2] Revert "tests/intel/xe_gt_freq: Fix freq_low_max test" Badal Nilawar
2024-06-14 10:07 ` [PATCH i-g-t 2/2] "tests/intel/xe_gt_freq: Fix freq_low_max test Badal Nilawar
2024-06-14 13:37 ` Kamil Konieczny
2024-06-14 14:19 ` Nilawar, Badal [this message]
2024-06-14 13:48 ` ✓ CI.xeBAT: success for " Patchwork
2024-06-14 13:57 ` ✓ Fi.CI.BAT: " Patchwork
2024-06-14 23:51 ` ✓ CI.xeFULL: " Patchwork
2024-06-16 21:19 ` ✗ Fi.CI.IGT: failure " 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=ce394992-ca36-4f9c-8cbd-6953825e4286@intel.com \
--to=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.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