Quoting Michal Wajdeczko (2017-08-04 17:27:12) > During debug we may want to investigate all communication > from the Guc. Add proper tracing macros in debug config. > > Signed-off-by: Michal Wajdeczko <michal.wajdeczko@xxxxxxxxx> > --- > drivers/gpu/drm/i915/intel_guc_ct.c | 19 +++++++++++++++++++ > 1 file changed, 19 insertions(+) > > diff --git a/drivers/gpu/drm/i915/intel_guc_ct.c b/drivers/gpu/drm/i915/intel_guc_ct.c > index 9f7fc5e..71daad3 100644 > --- a/drivers/gpu/drm/i915/intel_guc_ct.c > +++ b/drivers/gpu/drm/i915/intel_guc_ct.c > @@ -24,6 +24,12 @@ > #include "i915_drv.h" > #include "intel_guc_ct.h" > > +#ifdef CONFIG_DRM_I915_DEBUG > +#define CT_DEBUG_DRIVER(...) DRM_DEBUG_DRIVER(__VA_ARGS__) > +#else > +#define CT_DEBUG_DRIVER(...) > +#endif +1. If we only use a single Kconfig, or enabled them for CI anyway, we still run the risk of drowning in the noise. Flooding CI dmesg has many other unfortunate repercussions as well. Oh well, back to the ddebug / trace_debug wishlist. (Being able to dump the pertinent buffer on demand/error without flooding the test runner.) -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
