From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [PATCH i-g-t] kms_flip_tiling: [linear, X]<->[Y, Yf] tiling changes are not allowed
Date: Wed, 22 Apr 2015 17:23:11 +0100 [thread overview]
Message-ID: <5537CAEF.2020107@linux.intel.com> (raw)
In-Reply-To: <20150422160731.GT17348@nuc-i3427.alporthouse.com>
Hi,
On 04/22/2015 05:07 PM, Chris Wilson wrote:
> On Wed, Apr 22, 2015 at 05:00:27PM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> This matches the behaviour in kernel patch
>> "drm/i915/skl: Disallow tiling changes during page flip".
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> ---
>> tests/kms_flip_tiling.c | 23 ++++++++++++++---------
>> 1 file changed, 14 insertions(+), 9 deletions(-)
>>
>> diff --git a/tests/kms_flip_tiling.c b/tests/kms_flip_tiling.c
>> index 8345505..3eef4cc 100644
>> --- a/tests/kms_flip_tiling.c
>> +++ b/tests/kms_flip_tiling.c
>> @@ -63,7 +63,7 @@ fill_linear_fb(struct igt_fb *fb, data_t *data, drmModeModeInfo *mode)
>> }
>>
>> static void
>> -test_flip_changes_tiling(data_t *data, igt_output_t *output, uint64_t tiling)
>> +test_flip_changes_tiling(data_t *data, igt_output_t *output, uint64_t tiling, int expect)
>> {
>> struct igt_fb linear, tiled;
>> drmModeModeInfo *mode;
>> @@ -107,13 +107,15 @@ test_flip_changes_tiling(data_t *data, igt_output_t *output, uint64_t tiling)
>> /* flip to the linear buffer */
>> ret = drmModePageFlip(data->drm_fd, output->config.crtc->crtc_id,
>> fb_id, 0, NULL);
>> - igt_assert_eq(ret, 0);
>> + igt_assert_eq(ret, expect);
>>
>> - igt_wait_for_vblank(data->drm_fd, pipe);
>> + if (expect == 0) {
>
> I'd still accept ret == 0 since maybe one day it will work happily.
>
> So perhaps:
> if (ret) igt_assert_rq(ret, expect);
> igt_require(ret == 0);
> ?
Well would have to at least run the cleanup part before skipping, but
even before that I am not sure. That means test would skip today, and
who knows for how long in the future, and then soon no one kind of knows
what that means - is it good or bad?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-22 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 16:00 [PATCH i-g-t] kms_flip_tiling: [linear, X]<->[Y, Yf] tiling changes are not allowed Tvrtko Ursulin
2015-04-22 16:07 ` Chris Wilson
2015-04-22 16:23 ` Tvrtko Ursulin [this message]
2015-04-22 16:45 ` Chris Wilson
2015-04-23 9:05 ` Tvrtko Ursulin
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=5537CAEF.2020107@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=tvrtko.ursulin@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