From: Petri Latvala <petri.latvala@intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane: Reduce pixel format test execution time
Date: Thu, 24 Oct 2019 14:08:30 +0300 [thread overview]
Message-ID: <20191024110830.GC25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20191022125409.20175-1-stanislav.lisovskiy@intel.com>
On Tue, Oct 22, 2019 at 03:54:09PM +0300, Stanislav Lisovskiy wrote:
> > -----Original Message-----
> > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Ville Syrjala
> > Sent: maanantai 21. lokakuuta 2019 20.50
> > To: igt-dev@lists.freedesktop.org
> > Subject: [igt-dev] [PATCH i-g-t] tests/kms_plane: Reduce pixel format test execution
> > time
> >
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > By default reduce the set of colors we test by half, and only test all the YCbCr
> > range/encoding combinations for linear buffers. This should hopefully still provide
> > decent coverage with a big reduction in execution time.
> > The previous more extensive coverage is now hidden behind the --extended
> > command line argument.
> >
> > On KBL:
> > time kms_plane --r pixel-format-pipe-A-planes
> > - real 1m7,995s
> > + real 0m22,943s
> >
> > Further ideas for more reduction:
> > - Don't test on all planes (eg. on icl+ we could test on one hdr
> > plane, one sdr uv plane, and one sdr y plane)
> > - Don't test absolutely every pixel format + modifier combination
> > - Pipeline even deeper to make each color checked take only a single
> > frame (currently I think it should be taking two frames per color)
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Merged this. Thanks!
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-10-24 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 17:50 [igt-dev] [PATCH i-g-t] tests/kms_plane: Reduce pixel format test execution time Ville Syrjala
2019-10-21 18:38 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-10-21 23:26 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
[not found] ` <20191022125409.20175-1-stanislav.lisovskiy@intel.com>
2019-10-24 11:08 ` Petri Latvala [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=20191024110830.GC25209@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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