From: Zhipeng Gong <zhipeng.gong@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/3] tests/gem_exec_params: check the invalid flags for dual bsd ring
Date: Thu, 7 Aug 2014 15:49:24 +0800 [thread overview]
Message-ID: <1407397765-13316-3-git-send-email-zhipeng.gong@intel.com> (raw)
In-Reply-To: <1407397765-13316-1-git-send-email-zhipeng.gong@intel.com>
Signed-off-by: Zhipeng Gong <zhipeng.gong@intel.com>
---
tests/gem_exec_params.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tests/gem_exec_params.c b/tests/gem_exec_params.c
index 769969d..b18ef4e 100644
--- a/tests/gem_exec_params.c
+++ b/tests/gem_exec_params.c
@@ -126,6 +126,12 @@ igt_main
RUN_FAIL(EINVAL);
}
+ igt_subtest("invalid-bsd-ring") {
+ igt_require(gem_has_bsd2(fd));
+ execbuf.flags = I915_EXEC_BSD | I915_EXEC_BSD_MASK;
+ RUN_FAIL(EINVAL);
+ }
+
igt_subtest("rel-constants-invalid-ring") {
igt_require(gem_has_bsd(fd));
execbuf.flags = I915_EXEC_BSD | I915_EXEC_CONSTANTS_ABSOLUTE;
--
2.0.3
next prev parent reply other threads:[~2014-08-07 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 7:49 [PATCH i-g-t 0/3] tests: Add tests for new exec flags to export two bsd rings Zhipeng Gong
2014-08-07 7:49 ` [PATCH 1/3] i-g-t: check whether kernel has dual bsd ring Zhipeng Gong
2014-12-02 18:44 ` Rodrigo Vivi
2014-12-03 9:11 ` Daniel Vetter
2014-08-07 7:49 ` Zhipeng Gong [this message]
2014-12-02 18:45 ` [PATCH 2/3] tests/gem_exec_params: check the invalid flags for " Rodrigo Vivi
2014-08-07 7:49 ` [PATCH 3/3] test/gem_dummy_reloc_loop: add tests " Zhipeng Gong
2014-12-02 18:46 ` Rodrigo Vivi
2015-01-13 0:50 [PATCH i-g-t 0/3] tests: Add tests for new exec flags to export two bsd rings Zhipeng Gong
2015-01-13 0:50 ` [PATCH 2/3] tests/gem_exec_params: check the invalid flags for dual bsd ring Zhipeng Gong
2015-01-20 21:43 ` Rodrigo Vivi
2015-01-21 1:04 ` Gong, Zhipeng
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=1407397765-13316-3-git-send-email-zhipeng.gong@intel.com \
--to=zhipeng.gong@intel.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 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.