From: Ayaz A Siddiqui <ayaz.siddiqui@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Ayaz A Siddiqui <ayaz.siddiqui@intel.com>
Subject: [igt-dev] [PATCH i-g-t 0/2] Add check for FENCE based tiling support
Date: Sun, 2 Feb 2020 01:03:45 +0530 [thread overview]
Message-ID: <20200201193347.7432-1-ayaz.siddiqui@intel.com> (raw)
These tests are verifying the integrity of blitter render copy as well as
read write operations for tiling data on platform which has support of
FANCES. So a check has been added to skip the test if no of fences are
zero on the platform.
gem_render_tiled_blits: Test to check effects of different physical
address values on render copy is being developed as Kernel selftest.
Ayaz A Siddiqui (2):
i915/gem_tiled_pread_*: Add check for FENCE based tiling support
i915/gem_render_tiled_blits: Add check for hardware based FENCE
support
tests/i915/gem_render_tiled_blits.c | 1 +
tests/i915/gem_tiled_pread_basic.c | 2 +-
tests/i915/gem_tiled_pread_pwrite.c | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)
--
2.24.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-02-01 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 19:33 Ayaz A Siddiqui [this message]
2020-02-01 19:33 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_tiled_pread_*: Add check for FENCE based tiling support Ayaz A Siddiqui
2020-02-01 21:05 ` Dixit, Ashutosh
2020-02-02 10:26 ` Chris Wilson
2020-02-02 13:05 ` Siddiqui, Ayaz A
2020-02-01 19:33 ` [igt-dev] [PATCH i-g-t 2/2] i915/gem_render_tiled_blits: Add check for hardware based FENCE support Ayaz A Siddiqui
2020-02-01 21:20 ` Dixit, Ashutosh
2020-02-01 20:21 ` [igt-dev] ✓ Fi.CI.BAT: success for Add check for FENCE based tiling support Patchwork
2020-02-05 3:06 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20200201193347.7432-1-ayaz.siddiqui@intel.com \
--to=ayaz.siddiqui@intel.com \
--cc=igt-dev@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