public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Paulo Zanoni <przanoni@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: [PATCH igt 0/8] Make kms_fbc_crc useful again
Date: Thu,  7 May 2015 15:56:28 -0300	[thread overview]
Message-ID: <1431024996-2267-1-git-send-email-przanoni@gmail.com> (raw)

From: Paulo Zanoni <paulo.r.zanoni@intel.com>

After the recent IGT regressions and the FBC conversion to the
frontbuffer tracking infrastructure, kms_fbc_crc was not being that
useful anymore. So this series makes it useful again.

The first 2 patches are alternate forms of patches that I already sent
to the mailing list a few times. They are needed due to the Kernel FBC
changes. In the previous versions I was adding gem_sync() calls, but
now I'm just increasing the timeouts. I'm aware we want to have test
cases for both situations, but for now let's fix the ones we already
have with the least intrusive solution.

The other 6 patches are just for the CRC regression fix. Notice that
kms_fbc_crc is completely useless without this fix. Daniel has already
sent an earlier for this problem, but I believe my proposed solution
is more complete.

Of course, to make kms_fbc_crc actually useful we need to enable FBC
by default again, but we're not there yet.

Also notice that there's still no conversion to use lib/igt_draw, but
some of the reworks required by it are already on this series. I want
to land any possible conversion only after we fix the current known
regressions.

Thanks,
Paulo

Paulo Zanoni (8):
  tests/kms_fbc_crc: exec_nop() can also invalidate FBC
  tests/kms_fbc_crc: increase the FBC wait timeout
  tests/kms_fbc_crc: unify flip handling
  tests/kms_fbc_crc: refactor context handling code
  tests/kms_fbc_crc: extract check_crc()
  tests/kms_fbc_crc: make the blt test draw the same pattern
  tests/kms_fbc_crc: extract fill_mmap_{cpu,gtt}()
  tests/kms_fb_crc: fix the reference CRC checking

 tests/kms_fbc_crc.c | 193 +++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 129 insertions(+), 64 deletions(-)

-- 
2.1.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2015-05-07 18:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 18:56 Paulo Zanoni [this message]
2015-05-07 18:56 ` [PATCH igt 1/8] tests/kms_fbc_crc: exec_nop() can also invalidate FBC Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 2/8] tests/kms_fbc_crc: increase the FBC wait timeout Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 3/8] tests/kms_fbc_crc: unify flip handling Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 4/8] tests/kms_fbc_crc: refactor context handling code Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 5/8] tests/kms_fbc_crc: extract check_crc() Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 6/8] tests/kms_fbc_crc: make the blt test draw the same pattern Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 7/8] tests/kms_fbc_crc: extract fill_mmap_{cpu, gtt}() Paulo Zanoni
2015-05-07 18:56 ` [PATCH igt 8/8] tests/kms_fb_crc: fix the reference CRC checking Paulo Zanoni

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=1431024996-2267-1-git-send-email-przanoni@gmail.com \
    --to=przanoni@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@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