From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH i-g-t] kms_rotation_crc: 90 degree flip test is not a stress test
Date: Thu, 3 Aug 2017 14:09:59 +0100 [thread overview]
Message-ID: <33ff9af2-1a00-7adb-d40f-08e5900cdfe0@linux.intel.com> (raw)
In-Reply-To: <150176482238.20927.17251360853625186814@mail.alporthouse.com>
On 03/08/2017 13:53, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2017-08-03 13:42:50)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> To the best of my recollection the page flipping test was added
>> simply to start exercising page flips with 90/270 rotation.
>>
>> There is no need to do 60 flips which can take quite some time
>> because we test each pipe and then each fb geometry. And
>> calling this a stress test is also not matching the original
>> idea of the test.
>>
>> So remove the stress from the name and reduce the number of
>> flips to three only.
>
> Considering this found a bug, do we have an explicit test that says a
> rotated page flip takes no longer than a vblank (given the right
> conditions, i.e subsequent flips)?
That was just me misremembering how the test work, wasn't a bug. Once I
looked at the code in more detail I realized the test does much more
flipping than it initially seemed. Num_pipes * 4 fb geometries * 2
framebuffers * 60 flips. In total around 8 seconds of flipping per pipe.
So the 25 second runtime is in line with 3 pipes at 60Hz plus some test
setup time.
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-03 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 12:42 [PATCH i-g-t] kms_rotation_crc: 90 degree flip test is not a stress test Tvrtko Ursulin
2017-08-03 12:53 ` Chris Wilson
2017-08-03 13:09 ` Tvrtko Ursulin [this message]
2017-08-03 13:27 ` Chris Wilson
2017-08-03 13:41 ` Tvrtko Ursulin
2017-08-03 14:19 ` Chris Wilson
2017-08-03 14:33 ` Tvrtko Ursulin
2017-08-03 14:50 ` Chris Wilson
2017-08-03 15:23 ` Daniel Vetter
2017-08-04 8:43 ` [PATCH i-g-t v2] " Tvrtko Ursulin
2017-08-07 15:53 ` Daniel Vetter
2017-09-04 14:27 ` Tvrtko Ursulin
2017-09-04 14:36 ` Tvrtko Ursulin
2017-09-04 14:43 ` Daniel Vetter
2017-09-04 14:56 ` Tvrtko Ursulin
[not found] ` <20170907141307.GA15917@kdec5-desk.ger.corp.intel.com>
[not found] ` <804db97c-0746-3796-01c0-8d0b390528f5@linux.intel.com>
2017-09-07 15:07 ` Katarzyna Dec
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=33ff9af2-1a00-7adb-d40f-08e5900cdfe0@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=tursulin@ursulin.net \
/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