From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Thomas Wood <thomas.wood@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH i-g-t 4/8] kms_frontbuffer_tracking: Allow to skip suspend_resume sub test case.
Date: Wed, 18 Nov 2015 11:31:45 +0100 [thread overview]
Message-ID: <20151118103145.GN20799@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGRg1jQRqyoLbOe8XJseXfgd-8NQhUKafUgC128ELOB-Ew@mail.gmail.com>
On Mon, Nov 09, 2015 at 11:52:20AM -0200, Paulo Zanoni wrote:
> 2015-11-05 18:40 GMT-02:00 Ville Syrjälä <ville.syrjala@linux.intel.com>:
> > On Thu, Nov 05, 2015 at 06:34:07PM -0200, Paulo Zanoni wrote:
> >> 2015-11-05 16:53 GMT-02:00 Rodrigo Vivi <rodrigo.vivi@intel.com>:
> >> > There are few platforms with other suspend resume bugs that breaks
> >> > the full execution. So let's provide a way to skip suspend resume case.
> >>
> >> Well, I carry a local patch that completely disables suspend subtests
> >> for the tests that I usually run, so I really understand your pain.
> >> Suspend subtests take a long time to run, and they usually don't work
> >> on some of the preproduction machines I still use.
> >>
> >> But since this problem is not specific to kms_frontbuffer_tracking,
> >> maybe we could adopt an igt-wide solution here? Thomas, any idea here?
> >
> > -x suspend is what I tell piglit on one hsw I have here which hangs on s3.
>
> The problem with piglit is that it runs every single subtest as a
> separate test program invocation. For KMS tests this is a huge problem
> since it requires generating the reference CRCs every time and it also
> requires a modeset to restore fbcon every single time. For non-eDP the
> cost is not big, but for eDP it adds up: running a subset of only 70
> subtests on kms_frontbuffer_tracking, we go from 3:05 to 6:21 in total
> execution time.
We need to fix this. Generating the reference crc is hard, but getting rid
of fbcon and other setup overhead should be doable. Improving piglit
runtime means CI can run more tests, which means the test you're writing
might actually be used.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-18 10:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 18:53 [PATCH i-g-t 1/8] kms_frontbuffer_tracking: Increase the time we wait for PSR Rodrigo Vivi
2015-11-05 18:53 ` [PATCH i-g-t 2/8] kms_frontbuffer_tracking: Skip on unreliable CRC Rodrigo Vivi
2015-11-05 20:30 ` Paulo Zanoni
2015-11-18 10:27 ` Daniel Vetter
2015-12-02 1:10 ` Rodrigo Vivi
2015-12-03 7:50 ` Daniel Vetter
2015-11-05 18:53 ` [PATCH i-g-t 3/8] kms_frontbuffer_tracking: Allow pipe crc or sink crc individually Rodrigo Vivi
2015-11-05 21:00 ` Paulo Zanoni
2015-11-05 18:53 ` [PATCH i-g-t 4/8] kms_frontbuffer_tracking: Allow to skip suspend_resume sub test case Rodrigo Vivi
2015-11-05 20:34 ` Paulo Zanoni
2015-11-05 20:40 ` Ville Syrjälä
2015-11-09 13:52 ` Paulo Zanoni
2015-11-18 10:31 ` Daniel Vetter [this message]
2015-11-05 18:53 ` [PATCH i-g-t 5/8] kms_frontbuffer_tracking: Add option to allow running tescases with PSR disabled Rodrigo Vivi
2015-11-05 20:44 ` Paulo Zanoni
2015-11-05 18:53 ` [PATCH i-g-t 6/8] kms_frontbuffer_tracking: Add option to allow running tescases with FBC disabled Rodrigo Vivi
2015-11-05 18:53 ` [PATCH i-g-t 7/8] kms_psr_sink_crc: Fix no-psr option Rodrigo Vivi
2015-11-05 18:53 ` [PATCH i-g-t 8/8] kms_psr_sink_crc: Add suspend/resume sub test Rodrigo Vivi
2015-11-05 20:11 ` [PATCH i-g-t 1/8] kms_frontbuffer_tracking: Increase the time we wait for PSR Paulo Zanoni
2015-12-02 1:19 ` Rodrigo Vivi
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=20151118103145.GN20799@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.wood@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