On Mon, 6 Nov 2017 20:57:40 -0700 Michael Sartain <mikesart@xxxxxxxxxxxx> wrote: > trace-cmd report unloaded_system.dat | grep "seq=50856" > Xorg-666 [001] 850.248191: drm_vblank_event_queued: file=0xffff916525fcec00, crtc=0, seq=50856 > Xorg-666 [001] 850.263652: drm_vblank_event_queued: file=0xffff916525fcec00, crtc=0, seq=50856 > <idle>-0 [001] 850.264745: drm_vblank_event_delivered: file=0xffff916525fcec00, crtc=0, seq=50856 > <idle>-0 [001] 850.264753: drm_vblank_event_delivered: file=0xffff916525fcec00, crtc=0, seq=50856 > <idle>-0 [001] 850.264756: drm_vblank_event_delivered: file=0xffff916525fcec00, crtc=0, seq=50856 > <idle>-0 [001] 850.264758: drm_vblank_event: crtc=0, seq=50856 > > On a loaded system (running Unigine Heaven demo + glxgears -fullscreen), > the above happens most of the time, but there are several missing > drm_vblank_events and several drm_vblank_events that don't have any > matching drm_vblank_event_queued or delivered events. Example: > > trace-cmd report loaded_system.dat | grep "seq=93977" > <idle>-0 [001] 5161.664754: drm_vblank_event: crtc=0, seq=93977 > > This looks to me like we are missing events in the capture. Is this > possible? Is there any way to mitigate if so? Could it just be that the events were lost due to overwriting the buffers? Looks like the drm_vblank_event is the last of the series. It could be that the previous events for that seq was overwritten by newer events. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|