Comment 99 for bug 1690719

Is Mutter using cursor plane for updating the mouse cursor on screen, or something slow, like using normal 3D pipeline to update it?

Latter would mean that:
* Visible mouse updates are slowed down to application frame update speed when they're mixed with slow application frames in the GPU batch queue (FurMark on integrated GPU is good example of that)
* Much larger memory bandwidth usage overhead, because AFAIK most 3D drivers don't support partial screen updates, so all mouse updates would be fullscreen renders, instead of updates just for the cursor plane onscreen co-ordinates