On Tue, May 10, 2016 at 08:19:50PM +0300, Ville Syrjälä wrote: > > [46796.049127] [drm:drm_update_vblank_count] updating vblank count on crtc 1: current=72, diff=1, hw=72 hw_last=71 > > [46796.049129] [drm:drm_handle_vblank_events] vblank event on 73, current 73 > > Either we had a stale event in the queue, or something else is busted. > Did someone really request an event on seq==73? Yes, it uses an event a short while after the expected end of the test for two purposes: a timing check, to keep the vblank alive (for measuring the overhead of doing vblank_get on each query). -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
