From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>, 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 10:27:16 +0000 [thread overview]
Message-ID: <ebfddcea-8427-5d87-83e9-93a1fef024e6@linux.intel.com> (raw)
In-Reply-To: <20221107062329.1927534-1-ashutosh.dixit@intel.com>
On 07/11/2022 06:23, Ashutosh Dixit wrote:
> In igt@perf_pmu@frequency subtest, compare the requested freq reported by
> PMU not against the set freq but against the requested freq reported in
> sysfs. If requested freq differs from the set freq (even when min == max
> freq) for whatever reason, the sysfs requested freq should be closer to the
> PMU measured requested freq which should minimize sporadic failures.
>
> Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/6806
So this bug describes the failure looks like this:
Starting subtest: frequency
(perf_pmu:1798) CRITICAL: Test assertion failure function test_frequency, file ../tests/i915/perf_pmu.c:1636:
(perf_pmu:1798) CRITICAL: Failed assertion: (double)(min[0]) <= (1.0 + (tolerance)) * (double)(min_freq) && (double)(min[0]) >= (1.0 - (tolerance)) * (double)(min_freq)
(perf_pmu:1798) CRITICAL: 'min[0]' != 'min_freq' (347.914580 not within +5.0%/-5.0% tolerance of 300.000000)
Subtest frequency failed.
Which is this in code:
min_freq = igt_sysfs_get_u32(sysfs, "gt_RPn_freq_mhz");
...
/*
* Set GPU to min frequency and read PMU counters.
*/
igt_require(igt_sysfs_set_u32(sysfs, "gt_min_freq_mhz", min_freq));
igt_require(igt_sysfs_get_u32(sysfs, "gt_min_freq_mhz") == min_freq);
igt_require(igt_sysfs_set_u32(sysfs, "gt_max_freq_mhz", min_freq));
igt_require(igt_sysfs_get_u32(sysfs, "gt_max_freq_mhz") == min_freq);
igt_require(igt_sysfs_set_u32(sysfs, "gt_boost_freq_mhz", min_freq));
igt_require(igt_sysfs_get_u32(sysfs, "gt_boost_freq_mhz") == min_freq);
...
gem_quiescent_gpu(gem_fd); /* Idle to be sure the change takes effect */
spin = spin_sync_flags(gem_fd, ahnd, 0, I915_EXEC_DEFAULT);
slept = pmu_read_multi(fd[0], 2, start);
measured_usleep(batch_duration_ns / 1000);
slept = pmu_read_multi(fd[0], 2, val) - slept;
min[0] = 1e9*(val[0] - start[0]) / slept;
min[1] = 1e9*(val[1] - start[1]) / slept;
...
/*
* Restore min/max.
*/
igt_sysfs_set_u32(sysfs, "gt_min_freq_mhz", min_freq);
if (igt_sysfs_get_u32(sysfs, "gt_min_freq_mhz") != min_freq)
igt_warn("Unable to restore min frequency to saved value [%u MHz], now %u MHz\n",
min_freq, igt_sysfs_get_u32(sysfs, "gt_min_freq_mhz"));
close(fd[0]);
close(fd[1]);
put_ahnd(ahnd);
igt_info("Min frequency: requested %.1f, actual %.1f\n",
min[0], min[1]);
igt_info("Max frequency: requested %.1f, actual %.1f\n",
max[0], max[1]);
assert_within_epsilon(min[0], min_freq, tolerance);
Which means sysfs told the test which is the minimum frequency. But it really isn't - it turns out 350 MHz is the real minimum? Or setting of gt_max_freq_mhz/gt_boost_freq_mhz is not actually respected by SLPC? It sounds trivial to respect the minimum frequency so I don't see what is the excuse.
Regards,
Tvrtko
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> tests/i915/perf_pmu.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/tests/i915/perf_pmu.c b/tests/i915/perf_pmu.c
> index f363db2ba13..42b5b7bd6f2 100644
> --- a/tests/i915/perf_pmu.c
> +++ b/tests/i915/perf_pmu.c
> @@ -1546,7 +1546,7 @@ test_interrupts_sync(int gem_fd)
> static void
> test_frequency(int gem_fd)
> {
> - uint32_t min_freq, max_freq, boost_freq;
> + uint32_t min_freq, max_freq, boost_freq, min_req, max_req;
> uint64_t val[2], start[2], slept;
> double min[2], max[2];
> igt_spin_t *spin;
> @@ -1587,6 +1587,7 @@ test_frequency(int gem_fd)
>
> min[0] = 1e9*(val[0] - start[0]) / slept;
> min[1] = 1e9*(val[1] - start[1]) / slept;
> + min_req = igt_sysfs_get_u32(sysfs, "gt_cur_freq_mhz");
>
> igt_spin_free(gem_fd, spin);
> gem_quiescent_gpu(gem_fd); /* Don't leak busy bo into the next phase */
> @@ -1613,6 +1614,7 @@ test_frequency(int gem_fd)
>
> max[0] = 1e9*(val[0] - start[0]) / slept;
> max[1] = 1e9*(val[1] - start[1]) / slept;
> + max_req = igt_sysfs_get_u32(sysfs, "gt_cur_freq_mhz");
>
> igt_spin_free(gem_fd, spin);
> gem_quiescent_gpu(gem_fd);
> @@ -1633,12 +1635,12 @@ test_frequency(int gem_fd)
> igt_info("Max frequency: requested %.1f, actual %.1f\n",
> max[0], max[1]);
>
> - assert_within_epsilon(min[0], min_freq, tolerance);
> + assert_within_epsilon(min[0], min_req, tolerance);
> /*
> * On thermally throttled devices we cannot be sure maximum frequency
> * can be reached so use larger tolerance downards.
> */
> - __assert_within_epsilon(max[0], max_freq, tolerance, 0.15f);
> + __assert_within_epsilon(max[0], max_req, tolerance, 0.15f);
> }
>
> static void
next prev parent reply other threads:[~2022-11-07 10:27 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 ` Tvrtko Ursulin [this message]
2022-11-08 0:18 ` [igt-dev] [PATCH i-g-t] " Dixit, Ashutosh
2022-11-08 0:22 ` Dixit, Ashutosh
2022-11-08 0:57 ` Belgaumkar, Vinay
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=ebfddcea-8427-5d87-83e9-93a1fef024e6@linux.intel.com \
--to=tvrtko.ursulin@linux.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