public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/perf_pmu: Compare against requested freq in frequency subtest
Date: Mon, 7 Nov 2022 16:57:24 -0800	[thread overview]
Message-ID: <33646ce6-6692-1244-cb9f-4740105aadef@intel.com> (raw)
In-Reply-To: <87leoml2g4.wl-ashutosh.dixit@intel.com>


On 11/7/2022 4:22 PM, Dixit, Ashutosh wrote:
> On Mon, 07 Nov 2022 16:18:31 -0800, Dixit, Ashutosh wrote:
> Hi Vinay,
>
> A question for you below.
>
>> So I submitted this patch to repro the issue and to print out the requested
>> freq from sysfs:
>>
>> https://patchwork.freedesktop.org/series/110630/
>>
>> And we can see the output here:
>>
>> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8061/bat-dg2-11/igt@perf_pmu@frequency.html
>>
>> ```
>> IGT-Version: 1.26-g1bef4d081 (x86_64) (Linux: 6.1.0-rc4-CI_DRM_12352-gc55ac6a74bd1+ x86_64)
>> Starting subtest: frequency
>> Frequency: min=300, max=2050, boost=2050 MHz
>> Min frequency: requested 349.7, actual 349.7
>> Max frequency: requested 2048.0, actual 2048.0
>> Sysfs requested: min 350, max 2050
>> Stack trace:
>>    #0 ../../../usr/src/igt-gpu-tools/lib/igt_core.c:1908 __igt_fail_assert()
>>    #1 ../../../usr/src/igt-gpu-tools/tests/i915/perf_pmu.c:1656 __igt_unique____real_main2147()
>>    #2 ../../../usr/src/igt-gpu-tools/tests/i915/perf_pmu.c:2147 main()
>>    #3 [__libc_start_main+0xf3]
>>    #4 [_start+0x2e]
>> Subtest frequency: FAIL (2.212s)
>> ```
>>
>> So we clearly see the requested freq from sysfs is indeed 350 MHz so
>> SLPC/PCODE is not honoring the set min == max == boost freq (and PMU is
>> measuring what sysfs is showing). In general PCODE is the final arbiter in
>> such cases and we do occasionally see instances where set freq limits are
>> not honored.
>>
>> I would say if igt@perf_pmu@frequency is testing freq measured by PMU then
>> the patch below is correct. Whether SLPC/PCODE is honoring the set freq
>> limits should be tested in a SLPC test (which we also have).
> igt@perf_pmu@frequency sets 'min == max == boost == 300 MHz' but we still
> see the requested freq to be 350 MHz. Do we have a SLPC test covering this
> scenario or should we add one? This is failing on one of the DG2's.

Does adding a delay help (around 20 ms for the h2g to go through 
typically)? Also, is there a workload running when we change the 
min=max=boost to 300?

We already check these things in our SLPC selftests.

Thanks,

Vinay.

>
> Thanks.
> --
> Ashutosh

  reply	other threads:[~2022-11-08  0:57 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  6:23 [igt-dev] [PATCH i-g-t] tests/perf_pmu: Compare against requested freq in frequency subtest Ashutosh Dixit
2022-11-07  6:58 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-11-07  7:58 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-11-07 10:27 ` [igt-dev] [PATCH i-g-t] " Tvrtko Ursulin
2022-11-08  0:18   ` Dixit, Ashutosh
2022-11-08  0:22     ` Dixit, Ashutosh
2022-11-08  0:57       ` Belgaumkar, Vinay [this message]
2022-11-08  1:31         ` Dixit, Ashutosh
2022-11-08  9:24           ` Tvrtko Ursulin
2022-11-08 21:02             ` Belgaumkar, Vinay
2022-11-09  1:53               ` Dixit, Ashutosh
2022-11-10  1:37                 ` Belgaumkar, Vinay
2022-11-10  4:20                   ` Dixit, Ashutosh
2022-11-09  1:49             ` Dixit, Ashutosh
2022-11-09  6:03               ` Dixit, Ashutosh
  -- strict thread matches above, loose matches on Subject: below --
2022-11-08 19:06 Ashutosh Dixit
2022-11-19  2:00 Ashutosh Dixit
2022-11-21  9:09 ` Tvrtko Ursulin
2022-11-23  6:03   ` Dixit, Ashutosh
2022-11-24 12:42     ` Tvrtko Ursulin
2022-12-16  6:21       ` Dixit, Ashutosh
2022-12-16  9:37         ` Tvrtko Ursulin
2022-12-16 15:39           ` Rodrigo Vivi
2022-12-17  2:49             ` Dixit, Ashutosh
2022-12-19  8:46               ` Tvrtko Ursulin
2022-12-22 20:28                 ` Rodrigo Vivi
2022-12-23  9:22                   ` Tvrtko Ursulin
2022-12-23 15:39                     ` Rodrigo Vivi
2023-01-05 21:26                       ` Dixit, Ashutosh
2023-01-06 20:12                         ` Rodrigo Vivi
2023-01-06 20:39                           ` Belgaumkar, Vinay
2023-01-06 21:38                             ` Dixit, Ashutosh
2023-01-09 21:01                               ` Rodrigo Vivi
2023-01-10 19:49                                 ` Dixit, Ashutosh

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=33646ce6-6692-1244-cb9f-4740105aadef@intel.com \
    --to=vinay.belgaumkar@intel.com \
    --cc=ashutosh.dixit@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