<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [All - Bisected] slow cursor movements with atomic plane helpers" href="https://bugs.freedesktop.org/show_bug.cgi?id=88540#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [All - Bisected] slow cursor movements with atomic plane helpers" href="https://bugs.freedesktop.org/show_bug.cgi?id=88540">bug 88540</a> from <a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> Matt Roper</a> <pre>I believe this patch: <a href="http://lists.freedesktop.org/archives/dri-devel/2015-January/075670.html">http://lists.freedesktop.org/archives/dri-devel/2015-January/075670.html</a> will solve the immediate problem being reported here, at least for the existing Intel userspace I'm aware of. The problem here is that the display server wants to update the cursor faster than the display refresh rate and we were throttling the updates to vblank. The patch here removes that throttling for the case where the cursor is only being moved to a new position, but doesn't address the case where the cursor image changes. If there are any userspace display servers that also try to update the cursor image to a new framebuffer while reprogramming the cursor faster than the refresh rate, they'll still see the throttling. I'm not sure if there are any existing userspace display servers that work that way today.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>