Commit 9dd1a981 authored by Chris Wilson's avatar Chris Wilson

drm/i915/selftests: Include the start of each subtest in the GEM trace

Knowing the boundary of each subtest can be instrumental in digesting
the voluminous trace output and finding the critical piece of
information.
Signed-off-by: default avatarChris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: default avatarMichel Thierry <michel.thierry@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180713203529.1973-1-chris@chris-wilson.co.uk
parent 6710fcfc
...@@ -210,6 +210,8 @@ int __i915_subtests(const char *caller, ...@@ -210,6 +210,8 @@ int __i915_subtests(const char *caller,
return -EINTR; return -EINTR;
pr_debug(DRIVER_NAME ": Running %s/%s\n", caller, st->name); pr_debug(DRIVER_NAME ": Running %s/%s\n", caller, st->name);
GEM_TRACE("Running %s/%s\n", caller, st->name);
err = st->func(data); err = st->func(data);
if (err && err != -EINTR) { if (err && err != -EINTR) {
pr_err(DRIVER_NAME "/%s: %s failed with error %d\n", pr_err(DRIVER_NAME "/%s: %s failed with error %d\n",
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment