From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/2] tests/kms_chv_cursor_fail: Run the tests with fewer steps.
Date: Wed, 8 Jun 2016 16:47:48 +0200 [thread overview]
Message-ID: <b8adf4c9-fbe6-19ef-9441-d324bfda8379@linux.intel.com> (raw)
In-Reply-To: <20160608133558.GR4329@intel.com>
Op 08-06-16 om 15:35 schreef Ville Syrjälä:
> On Wed, Jun 08, 2016 at 03:23:33PM +0200, Maarten Lankhorst wrote:
>> Op 08-06-16 om 15:12 schreef Ville Syrjälä:
>>> On Wed, Jun 08, 2016 at 01:25:32PM +0200, Maarten Lankhorst wrote:
>>>> This reduces the runtime of the tests from ~200s on my 30 fps 4k panel
>>>> to 10s.
>>> Does it still find the problem reliably on CHV pipe C (if you remove the
>>> kernel w/a)?
>> Yeah, a single coordinate is enough to trigger the fifo underrun. Rest is probably still slightly overkill. :)
> Hmm. IIRC it wasn't quite that easy to trigger on my CHV. Sometime
> it survived for a few iterations. But I'm too lazy to retest it now,
> so I'll take your word for it.
>
Weird, even kms_cursor_crc random test triggered it for me on the first try with negative coordinates.
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-08 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 11:25 [PATCH i-g-t 1/2] tests/kms_chv_cursor_fail: Remove extra igt_pipe_crc_start Maarten Lankhorst
2016-06-08 11:25 ` [PATCH i-g-t 2/2] tests/kms_chv_cursor_fail: Run the tests with fewer steps Maarten Lankhorst
2016-06-08 13:12 ` Ville Syrjälä
2016-06-08 13:23 ` Maarten Lankhorst
2016-06-08 13:35 ` Ville Syrjälä
2016-06-08 14:47 ` Maarten Lankhorst [this message]
2016-06-08 14:52 ` Ville Syrjälä
2016-06-13 13:45 ` Maarten Lankhorst
2016-06-08 13:14 ` [PATCH i-g-t 1/2] tests/kms_chv_cursor_fail: Remove extra igt_pipe_crc_start Ville Syrjälä
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=b8adf4c9-fbe6-19ef-9441-d324bfda8379@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.