This latest pull request provides fine-tuned frame-buffer flushing and tracking, refactoring of state check dumper code, cleaning up various code, refactoring the watermark programming, GPU scheduler and priority boosting for flips, the frame-buffer compression code is now more atomic, and there is the initial KVM-GVT framework but it's not yet complete.
Yes, the Intel Graphics Virtualization Technology (GVT) code for the DRM driver is finally getting into shape and mainlined! GVT allows exposing a virtual GPU to VMs, either one VM to one GPU or multiple VMs to the same GPU. The GVT work has been for supporting the graphics on both Xen and KVM.
Intel DRM maintainer Daniel Vetter also noted in today's pull request that there will still be a super-late GVT pull request with the rest of the work. More details on all of the changes today via this pull request.