drm/i915: Print the condition causing GEM_BUG_ON
It is easier to categorize and debug bugs if the failed condition is in plain sight in the actual dmesg output. Make it so. Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Marta Lofstedt <marta.lofstedt@intel.com> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Marta Lofstedt <marta.lofstedt@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20171116083954.3357-1-mika.kuoppala@linux.intel.com
This commit is contained in:
parent
34cc9efc27
commit
d5653ec322
|
@ -28,7 +28,11 @@
|
|||
#include <linux/bug.h>
|
||||
|
||||
#ifdef CONFIG_DRM_I915_DEBUG_GEM
|
||||
#define GEM_BUG_ON(expr) BUG_ON(expr)
|
||||
#define GEM_BUG_ON(condition) do { if (unlikely((condition))) { \
|
||||
printk(KERN_ERR "GEM_BUG_ON(%s)\n", __stringify(condition)); \
|
||||
BUG(); \
|
||||
} \
|
||||
} while(0)
|
||||
#define GEM_WARN_ON(expr) WARN_ON(expr)
|
||||
|
||||
#define GEM_DEBUG_DECL(var) var
|
||||
|
|
Loading…
Reference in New Issue