From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Karthik B S <karthik.b.s@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks
Date: Thu, 29 Apr 2021 18:32:45 +0300 [thread overview]
Message-ID: <YIrRnQo3Fgpz0s+3@intel.com> (raw)
In-Reply-To: <a5ad5d3f-8f59-2e0b-d648-eb3ead077141@intel.com>
On Thu, Apr 29, 2021 at 11:07:53AM +0530, Karthik B S wrote:
> On 4/28/2021 3:55 AM, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Check the flip timestamp from the event (not the time we got the
> > event) against the vblank timestamps. Also if things are going
> > well we should expect the flip timestamp to in fact match the
> > first vblank timestamp, so allow them to be equal.
>
> Hi,
>
> During the initial implementation, the timestamp returned by the kernel
> was vblank timestamp and we were not sending back the flip timestamp.
>
> So we were calculating the time in the event rather than using the event
> timestamp.
That approach doesn't make too much sense since the two vblank
timestamps we're comparing against could both be in the future.
That happens if the flip is completed already during the first vblank.
But I haven't actually checked when the hw completes the flip when
scheduled during a vblank.
>
> Is this now updated to return the flip timestamp? If not, we would
> always have flip time stamp same as the previous vblank time stamp?
Looks like it just returns the last stored timestamp as before.
Which doesn't really make sense. At the very least we should
make sure the timestam and seq number are updated to reflect
the current frame. So if we do something like
1. wait for vblank
2. wait for several frames
3. async flip
then the event would now carry the timestamp from that ancient
vblank wait. Well, at least that's how it looks from the code,
still need to double check it. And the test should probably be
extended to catch stuff like that.
--
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:[~2021-04-29 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 22:25 [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Ville Syrjala
2021-04-27 23:12 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2021-04-28 2:37 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_async_flips: Fix flip timestamp checks (rev2) Patchwork
2021-04-28 5:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-04-28 14:38 ` [igt-dev] [PATCH i-g-t] tests/kms_async_flips: Fix flip timestamp checks Juha-Pekka Heikkila
2021-04-29 5:37 ` Karthik B S
2021-04-29 15:32 ` Ville Syrjälä [this message]
2021-05-04 11:12 ` Karthik B S
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=YIrRnQo3Fgpz0s+3@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@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