<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - xf86-video-amdgpu - commit 0d60233d introduced stuttering with mouse cursor operations" href="https://bugs.freedesktop.org/show_bug.cgi?id=109332#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - xf86-video-amdgpu - commit 0d60233d introduced stuttering with mouse cursor operations" href="https://bugs.freedesktop.org/show_bug.cgi?id=109332">bug 109332</a> from <a class="email" href="mailto:nicholas.kazlauskas@amd.com" title="Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>"> Nicholas Kazlauskas</a> <pre>In this case it's not actually the mouse operations themselves causing the stuttering but the framebuffer change. This is a known limitation with the async plane updates API in DRM and not something we can really fix in DC until there's a better API for async updates. The page-flip IOCTL advertises itself as non-blocking but in reality it's not - if there's any commit work touching the plane it's going to be blocked until that finishes and that'll be any non asynchronous cursor update, gamma update, property update, or anything else that occurs. This is what the stuttering comes from. So while it's a valid use of the cursor UAPI to double buffer cursors it's not something I'd really recommend doing for an atomic driver with how DRM is currently setup. Maybe this can be a configurable option in the meantime? I'm not sure how much work that would be to add and maintain, though.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>