From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
tomeu.vizoso@collabora.com
Subject: Re: [PATCH i-g-t v4 6/6] tests/kms_ccs: Test case for wrong aux buffer stride size
Date: Mon, 30 Oct 2017 17:59:26 +0200 [thread overview]
Message-ID: <20171030155926.GQ10981@intel.com> (raw)
In-Reply-To: <20171003105713.GA22208@ahiler-desk1.ger.corp.intel.com>
On Tue, Oct 03, 2017 at 01:57:13PM +0300, Arkadiusz Hiler wrote:
> On Wed, Sep 27, 2017 at 03:34:19PM -0300, Gabriel Krisman Bertazi wrote:
> > Two scenarios tested:
> > - unaligned stride
> > - Stride too small
> >
> > Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
>
> Fails on APL
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_260/shard-apl2/igt@kms_ccs@pipe-A-bad-aux-stride.html
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_260/shard-apl8/igt@kms_ccs@pipe-B-bad-aux-stride.html
>
> Works just fine on KBL though
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_260/shard-kbl1/igt@kms_ccs@pipe-A-bad-aux-stride.html
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_260/shard-kbl1/igt@kms_ccs@pipe-B-bad-aux-stride.html
Looks like the test has the addfb2 vs. render_fb() order wrong. The bad
stride could make render_fb/ccs() do somehting unexpected.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-30 15:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 18:34 [PATCH i-g-t v4 1/6] tests/kms_ccs: Test pipes other than pipe A Gabriel Krisman Bertazi
2017-09-27 18:34 ` [PATCH i-g-t v4 2/6] lib/igt_kms: Fix off-by-one bug on skip of missing pipe Gabriel Krisman Bertazi
2017-09-28 8:33 ` Petri Latvala
2017-09-27 18:34 ` [PATCH i-g-t v4 3/6] tests/kms_ccs: Prevent segfault if pipe is not supported Gabriel Krisman Bertazi
2017-10-03 10:49 ` Arkadiusz Hiler
2017-10-03 16:07 ` Ben Widawsky
2017-09-27 18:34 ` [PATCH i-g-t v4 4/6] tests/kms_ccs: Test case where the CCS buffer was not provided Gabriel Krisman Bertazi
2017-10-03 11:32 ` Arkadiusz Hiler
2017-10-03 16:35 ` Ben Widawsky
2017-10-09 6:14 ` Gabriel Krisman Bertazi
2017-10-30 16:02 ` Ville Syrjälä
2017-10-31 1:33 ` Gabriel Krisman Bertazi
2017-09-27 18:34 ` [PATCH i-g-t v4 5/6] tests/kms_ccs: Test case where CCS is on a different BO Gabriel Krisman Bertazi
2017-10-03 11:00 ` Arkadiusz Hiler
2017-10-03 16:38 ` Ben Widawsky
2017-10-09 6:18 ` Gabriel Krisman Bertazi
2017-09-27 18:34 ` [PATCH i-g-t v4 6/6] tests/kms_ccs: Test case for wrong aux buffer stride size Gabriel Krisman Bertazi
2017-10-03 10:57 ` Arkadiusz Hiler
2017-10-30 15:59 ` Ville Syrjälä [this message]
2017-10-03 16:40 ` Ben Widawsky
2017-10-09 6:03 ` Gabriel Krisman Bertazi
2017-10-30 16:04 ` Ville Syrjälä
2017-09-27 18:58 ` ✓ Fi.CI.BAT: success for series starting with [v4,1/6] tests/kms_ccs: Test pipes other than pipe A Patchwork
2017-09-27 23:42 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-09-28 16:06 ` Patchwork
2017-10-03 10:44 ` [PATCH i-g-t v4 1/6] " Arkadiusz Hiler
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=20171030155926.GQ10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomeu.vizoso@collabora.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