On Wed, 2023-06-28 at 14:15 +0000, Simon Ser wrote: > I think we should drop the CRTC_X/CRTC_Y properties for hotspot-aware cursor > planes. > The drivers aren't going to do anything with these, and exposing them to user- > space > makes it sound like user-space controls the position of the plane, but it really > doesn't. I think we talked about this before. The CRTC_X/CRTC_Y properties are absolutely being used and they're respected when the rendering is done guest-side - the system will be pretty broken if the client sets the crtc x/y properties to somewhere where the mouse isn't though. An argument could be made that crtc x/y properties should be removed on the cursor plane in drivers for para-virtualized hardware and instead replaced with mouse_position x/y properties that do exactly what crtc x/y properties do but make it explicit what they really are on a cursor plane. z
