public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/perf: dramatically loosen expectations on oa-exponents
Date: Mon, 30 Mar 2020 17:39:11 +0300	[thread overview]
Message-ID: <16e5476c-74a4-2aeb-19a4-9612fcc29369@intel.com> (raw)
In-Reply-To: <158557648695.3228.12905531047246276873@build.alporthouse.com>

On 30/03/2020 16:54, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2020-03-30 13:48:34)
>> This test really quite flaky because it expects HW to emit reports
>> following pretty much exactly the specified timer. And there are lots
>> of reasons the HW might not be able to meet the timer deadline. The
>> design is such that it's expected to not always meet the timer.
>>
>> We just want to verify that the HW was configured properly, so loosen
>> the checks to half the reports (of 30) meeting the timer deadline.
>>
>> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> ---
>>   tests/perf.c | 10 ++++++++--
>>   1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/perf.c b/tests/perf.c
>> index 442d89fb..023829fc 100644
>> --- a/tests/perf.c
>> +++ b/tests/perf.c
>> @@ -1742,8 +1742,14 @@ test_oa_exponents(void)
>>   
>>                  igt_debug("matches=%u/%u\n", matches, n_timer_reports - 1);
>>   
>> -               /* Allow for a couple of errors. */
>> -               igt_assert_lte(n_timer_reports - 3, matches);
>> +               /*
>> +                * Expect half the reports to match the timing
>> +                * expectation. The results are quite erratic because
>> +                * the condition under which the HW reaches
>> +                * expectations depends on memory controller pressure
>> +                * etc...
>> +                */
>> +               igt_assert_lte(n_timer_reports / 2, matches);
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> This will check for gross errors and so detect if we misconfigure the
> HW.
>
> What you might like to try is to look at the distribution of intervals,
> and compare the median against your expectations.
> -Chris

Yeah... It's quite annoying, sometimes the unit skips a deadline and 
tries to make it up right after...

Last time I checked the median didn't really help.


-Lionel

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-03-30 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 12:48 [igt-dev] [PATCH i-g-t] tests/perf: dramatically loosen expectations on oa-exponents Lionel Landwerlin
2020-03-30 13:29 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-30 13:54 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-03-30 14:39   ` Lionel Landwerlin [this message]
2020-03-31  3:11 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=16e5476c-74a4-2aeb-19a4-9612fcc29369@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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