summaryrefslogtreecommitdiff
path: root/lib/igt_core.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2015-03-26 08:11:43 +0000
committerChris Wilson <chris@chris-wilson.co.uk>2015-03-26 08:15:19 +0000
commit7763349a9a878ca58de4fb559edcbf81040da07b (patch)
treef373c328ad78b8645d545aa5ec19a930ed9fe7ae /lib/igt_core.c
parentc666a19e0c16821a1ccd2a2ea7dda549d19c67d1 (diff)
igt/gem_concurrent_blit: Separate out the combinatorial explosion
Apparently nobody else likes testing and debugging GEM coherency issues. However, this also means that QA is skipping these vital tests. Split out a set of canaries into igt/gem_concurrent_blit and keep the rest in igt/gem_concurrent_all. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89497 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'lib/igt_core.c')
-rw-r--r--lib/igt_core.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/lib/igt_core.c b/lib/igt_core.c
index 61b3a338..7c68d4eb 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -248,6 +248,11 @@ static struct {
} log_buffer;
static pthread_mutex_t log_buffer_mutex = PTHREAD_MUTEX_INITIALIZER;
+const char *igt_test_name(void)
+{
+ return command_str;
+}
+
static void _igt_log_buffer_append(char *line)
{
pthread_mutex_lock(&log_buffer_mutex);