Dave Airlie <airlied@xxxxxxxxx> writes: > On 6 February 2018 at 06:32, Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx> wrote: >> On Sat, Feb 03, 2018 at 08:14:48AM +0000, Keith Packard wrote: >>> Dhinakaran Pandiyan <dhinakaran.pandiyan@xxxxxxxxx> writes: >>> >>> > From: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@xxxxxxxxx> >>> > >>> > drm_vblank_count() has an u32 type returning what is a 64-bit vblank count. >>> > The effect of this is when drm_wait_vblank_ioctl() tries to widen the user >>> > space requested vblank sequence using this clipped 32-bit count(when the >>> > value is >= 2^32) as reference, the requested sequence remains a 32-bit >>> > value and gets queued like that. However, the code that checks if the >>> > requested sequence has passed compares this against the 64-bit vblank >>> > count. >>> >>> For patches 1-7: >>> >>> Reviewed-by: Keith Packard <keithp@xxxxxxxxxx> >> >> Dave, ack to merge them through drm-intel-next-queued ? > > Ack. do we know if any of those need to be in -fixes? All patches merged to drm-intel-next-queued. Thanks for the patches, reviews and acks. > > or too early to tell? > > Dave. > _______________________________________________ > dri-devel mailing list > dri-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/dri-devel _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
