Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Koppuravuri, Ravi Kishore" <ravi.kishore.koppuravuri@intel.com>
To: "Anirban, Sk" <sk.anirban@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH] tests/xe_pmu: Fix frequency stashing issue
Date: Mon, 28 Apr 2025 11:12:12 +0530	[thread overview]
Message-ID: <15c13750-e1d6-41b0-80de-dd9512b24534@intel.com> (raw)
In-Reply-To: <3f88eb7e-f2e9-4b45-8b6d-61156db5b2e4@intel.com>

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

Hi,

On 28-04-2025 11:06, Anirban, Sk wrote:
>
>
> On 25-04-2025 23:36, sk.anirban@intel.com wrote:
>> From: Sk Anirban <sk.anirban@intel.com>
>>
>> Resolved the frequency stashing problem by accurately
>> dereferencing the pointers, ensuring the minimum and
>> maximum frequencies are correctly restored.
>>
>> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
>> ---
>>   tests/intel/xe_pmu.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/intel/xe_pmu.c b/tests/intel/xe_pmu.c
>> index 589c7cbde..094dc0c6c 100644
>> --- a/tests/intel/xe_pmu.c
>> +++ b/tests/intel/xe_pmu.c
>> @@ -527,8 +527,8 @@ static void stash_gt_freq(int fd, uint32_t 
>> **stash_min, uint32_t **stash_max)
>>       igt_skip_on(*stash_min == NULL || *stash_max == NULL);
>>         xe_for_each_gt(fd, gt) {
>> -        *stash_min[gt] = xe_gt_get_freq(fd, gt, "min");
>> -        *stash_max[gt] = xe_gt_get_freq(fd, gt, "max");
>> +        (*stash_min)[gt] = xe_gt_get_freq(fd, gt, "min");
>> +        (*stash_max)[gt] = xe_gt_get_freq(fd, gt, "max");
>>       }
>>   }
>
It looks good to me.
Reviewed-by: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>

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

  reply	other threads:[~2025-04-28  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 18:06 [PATCH] tests/xe_pmu: Fix frequency stashing issue sk.anirban
2025-04-25 19:28 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-04-25 19:34 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-04-28 15:18   ` Anirban, Sk
2025-04-25 19:53 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-26  5:39 ` ✓ i915.CI.Full: " Patchwork
2025-04-26  9:05 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-28  5:36 ` [PATCH] " Anirban, Sk
2025-04-28  5:42   ` Koppuravuri, Ravi Kishore [this message]
2025-04-28  8:58   ` 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=15c13750-e1d6-41b0-80de-dd9512b24534@intel.com \
    --to=ravi.kishore.koppuravuri@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sk.anirban@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