From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] tests/kms_setmode: Request the initial vbl count with RELATIVE instead of ABSOLUTE
Date: Tue, 6 Nov 2018 20:40:03 +0200 [thread overview]
Message-ID: <20181106184003.GF9144@intel.com> (raw)
In-Reply-To: <154152232795.6179.12556322833653266565@skylake-alporthouse-com>
On Tue, Nov 06, 2018 at 04:38:48PM +0000, Chris Wilson wrote:
> Quoting Ville Syrjala (2018-11-06 16:19:42)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Asking for the initial vblank count by specifying and absolute vblank count of 0
> > doesn't make much sense. Switch to a relative query instead.
> >
> > It doesn't look like we care about lining up on the first vblank boundary so
> > we can just drop the NEXTONMISS flag. Only the relative timestamps of the
> > events will matter.
>
> I had to do a double take as quite often we care about submitting the
> workload before the next vblank, but no you are quite correct in this
> case so long as the next request is submitted within the next frame it
> should be fine and not miss a response.
>
> To catch the error during setup, we could do something like
>
> for (n = 0; n < CALIBRATE_TS_STEPS; n++) {
> drmVBlank check;
>
> ++wait.request.sequence;
> do_or_die(drmWaitVBlank(drm_fd, &wait));
>
> /* Double check that haven't already missed the vblank */
> memset(&check, 0, sizeof(check));
> check.request.type = kmstest_get_vblank_flag(crtc_idx);
> check.request.type |= DRM_VBLANK_RELATIVE;
> do_or_die(drmWaitVBlank(drm_fd, &check));
>
> igt_assert(!vblank_after(check.reply.sequence, wait.request.sequence));
> }
Isn't the 'igt_assert_eq(ev.sequence, last_seq + 1);' sufficient
to catch that?
>
> >
> > v2: Drop the NEXTONMISS (Daniel)
> >
> > Cc: Daniel Vetter <daniel@ffwll.ch>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> For both, but do consider the value of checking our setup.
> -Chris
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-11-06 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 16:19 [igt-dev] [PATCH i-g-t 1/3] lib/debugfs: Fix wraparound handling for crc frame counter check Ville Syrjala
2018-11-06 16:19 ` [igt-dev] [PATCH i-g-t 2/3] tests/kms_setmode: Request the initial vbl count with RELATIVE instead of ABSOLUTE Ville Syrjala
2018-11-06 16:38 ` Chris Wilson
2018-11-06 16:57 ` Daniel Vetter
2018-11-06 17:02 ` Ville Syrjälä
2018-11-06 18:40 ` Ville Syrjälä [this message]
2018-11-06 19:27 ` Chris Wilson
2018-11-06 16:19 ` [igt-dev] [PATCH i-g-t 3/3] tests/kms_flip: " Ville Syrjala
2018-11-06 16:58 ` [igt-dev] [PATCH i-g-t 1/3] lib/debugfs: Fix wraparound handling for crc frame counter check Daniel Vetter
2018-11-06 17:11 ` Chris Wilson
2018-11-07 19:19 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] " Patchwork
2018-11-08 7:20 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20181106184003.GF9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.