mirror of https://gitee.com/openkylin/linux.git
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: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Michel Thierry <michel.thierry@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180713203529.1973-1-chris@chris-wilson.co.uk
This commit is contained in:
parent
6710fcfca5
commit
9dd1a981a2
|
@ -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",
|
||||||
|
|
Loading…
Reference in New Issue