public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: martin.peres@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v1] igt/kms_flip: Use actual vblank_interval instead of expected.
Date: Wed, 4 Sep 2019 10:45:42 +0200	[thread overview]
Message-ID: <31b04e6e-1ce3-7c9c-d871-4c5a5f82837c@linux.intel.com> (raw)
In-Reply-To: <20190628121650.18519-1-stanislav.lisovskiy@intel.com>

Op 28-06-2019 om 14:16 schreef Stanislav Lisovskiy:
> If we are not currently failing at calibration stage, when we
> detect that actual vblank interval takes longer than expected
> according to the modeline, then we should not fail here as well.
>
> Vblank interval can be different from expected one depending on
> clocking used.
>
> Probably we need to have some criteria how much vblank interval
> is allowed to be different, however currently we don't fail in
> calibration_ts but simply print that it is different, while
> later during *-vs-vblank-race we do, even though the reason is
> the same.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103060
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>  tests/kms_flip.c | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 2a158d97..a47938cd 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -417,7 +417,6 @@ static double mode_frame_time(const struct test_output *o)
>  
>  static double actual_frame_time(const struct test_output *o)
>  {
> -	igt_assert(o->flags & TEST_CHECK_TS);
>  	return o->vblank_interval;
>  }
>  
> @@ -740,8 +739,8 @@ static unsigned int run_test_step(struct test_output *o)
>  		 * we waited for two vblanks, so verify that
>  		 * we were blocked for ~1-2 frames.
>  		 */
> -		igt_assert_f(end - start > 0.9 * mode_frame_time(o) &&
> -			     end - start < 2.1 * mode_frame_time(o),
> +		igt_assert_f(end - start > 0.9 * actual_frame_time(o) &&
> +			     end - start < 2.1 * actual_frame_time(o),
>  			     "wait for two vblanks took %lu usec (frame time %f usec)\n",
>  			     end - start, mode_frame_time(o));
>  		join_vblank_wait_thread();
> @@ -1545,8 +1544,8 @@ igt_main
>  					"single-buffer-flip-vs-dpms-off-vs-modeset" },
>  		{ 30, TEST_FLIP | TEST_NO_2X_OUTPUT | TEST_DPMS_OFF_OTHERS , "dpms-off-confusion" },
>  		{ 0, TEST_ENOENT | TEST_NOEVENT, "nonexisting-fb" },
> -		{ 10, TEST_DPMS_OFF | TEST_DPMS | TEST_VBLANK_RACE, "dpms-vs-vblank-race" },
> -		{ 10, TEST_MODESET | TEST_VBLANK_RACE, "modeset-vs-vblank-race" },
> +		{ 10, TEST_DPMS_OFF | TEST_DPMS | TEST_VBLANK_RACE | TEST_CHECK_TS, "dpms-vs-vblank-race" },
> +		{ 10, TEST_MODESET | TEST_VBLANK_RACE | TEST_CHECK_TS, "modeset-vs-vblank-race" },
>  		{ 0, TEST_BO_TOOBIG | TEST_NO_2X_OUTPUT, "bo-too-big" },
>  		{ 10, TEST_FLIP | TEST_SUSPEND, "flip-vs-suspend" },
>  	};

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

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

      parent reply	other threads:[~2019-09-04  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 12:16 [igt-dev] [PATCH i-g-t v1] igt/kms_flip: Use actual vblank_interval instead of expected Stanislav Lisovskiy
2019-06-28 18:42 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-06-29  6:27 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-09-04  8:45 ` Maarten Lankhorst [this message]

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=31b04e6e-1ce3-7c9c-d871-4c5a5f82837c@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@intel.com \
    --cc=stanislav.lisovskiy@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