From: Eric Anholt <eric@anholt.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>,
Intel GFX discussion <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/2] igt: Add VC4 purgeable BO tests
Date: Wed, 27 Sep 2017 11:08:53 -0700 [thread overview]
Message-ID: <877ewkj9oq.fsf@anholt.net> (raw)
In-Reply-To: <20170927115118.23170-3-boris.brezillon@free-electrons.com>
[-- Attachment #1.1: Type: text/plain, Size: 384 bytes --]
Boris Brezillon <boris.brezillon@free-electrons.com> writes:
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Another test we should have: Queue up a big rendering job (Copy a
2048x2048@32bpp BO?), mark the source purgeable, force the purge, wait
for rendering, make sure we correctly rendered, and maybe have some
sanity-checking of purgeable state of the BO.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-27 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 11:51 [PATCH i-g-t 0/2] igt: Add a testsuite to validate VC4 MADV ioctl Boris Brezillon
2017-09-27 11:51 ` [PATCH i-g-t 1/2] igt: Add a helper function to mark BOs purgeable Boris Brezillon
2017-09-27 11:51 ` [PATCH i-g-t 2/2] igt: Add VC4 purgeable BO tests Boris Brezillon
2017-09-27 11:57 ` Petri Latvala
2017-09-27 12:43 ` Boris Brezillon
2017-09-27 12:07 ` Chris Wilson
2017-09-27 12:41 ` Boris Brezillon
2017-09-27 12:50 ` Chris Wilson
2017-09-27 13:19 ` Boris Brezillon
2017-09-27 18:05 ` Eric Anholt
2017-09-27 18:08 ` Eric Anholt [this message]
2017-09-27 12:25 ` ✓ Fi.CI.BAT: success for igt: Add a testsuite to validate VC4 MADV ioctl Patchwork
2017-09-27 15:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-09-28 16:17 ` Patchwork
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=877ewkj9oq.fsf@anholt.net \
--to=eric@anholt.net \
--cc=boris.brezillon@free-electrons.com \
--cc=intel-gfx@lists.freedesktop.org \
/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