From: Sean Paul <seanpaul@xxxxxxxxxxxx> Hey all, I'm back with another trace events patchset. My first attempt [1] went better than expected, with enthusiasm for the idea and distain for the implementation. As promised, I went through and added proper trace events. Before I get _too_ far, I wanted to post this set to get feedback on the direction I'm going. I've gone back and forth on whether to introduce a bunch of trace systems vs using the trace class enum. I've settled on the trace class enum since it seems more extensible and easier to use in production that just having the blunt "enable this system", or the tedious "enable each event I'm interested in individually" methods. So, consider this one an RFC unless we're all in agreement, in which case we should apply it :) Sean [1]- https://patchwork.freedesktop.org/patch/335350/ Sean Paul (6): drm: trace: Make the vblank queued/delivered events classed drm: trace: Introduce drm_trace() and trace event classes drm: trace: Add trace events for atomic state lifetime drm: trace: Add crtc state trace events drm: trace: Add connector state tracing drm: trace: Add plane state tracing Documentation/gpu/drm-internals.rst | 9 + drivers/gpu/drm/drm_atomic.c | 61 ++- drivers/gpu/drm/drm_trace.h | 563 ++++++++++++++++++++++++++-- drivers/gpu/drm/drm_vblank.c | 8 +- 4 files changed, 609 insertions(+), 32 deletions(-) -- Sean Paul, Software Engineer, Google / Chromium OS _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
