We can add taint from multiple places, printing the caller allows us to
have a better overview of what exactly caused us to do the tainting.
Suggested-by: Michal Wajdeczko <michal.wajdeczko@xxxxxxxxx>
Signed-off-by: Michał Winiarski <michal.winiarski@xxxxxxxxx>
Cc: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
Cc: Michal Wajdeczko <michal.wajdeczko@xxxxxxxxx>
Cc: Petri Latvala <petri.latvala@xxxxxxxxx>
---
drivers/gpu/drm/i915/i915_utils.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/i915_utils.h b/drivers/gpu/drm/i915/i915_utils.h
index 03a73d2bd50d..1ed5c47eae8f 100644
--- a/drivers/gpu/drm/i915/i915_utils.h
+++ b/drivers/gpu/drm/i915/i915_utils.h
@@ -444,6 +444,7 @@ static inline void add_taint_for_CI(unsigned int taint)
* CI checks the taint state after every test and will reboot
* the machine if the kernel is tainted.
*/
+ pr_info("CI taint: %ps\n", __builtin_return_address(0));
add_taint(taint, LOCKDEP_STILL_OK);
}
--
2.27.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
