<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu.dc=1 shows performance issues with Xorg compositors when moving windows" href="https://bugs.freedesktop.org/show_bug.cgi?id=106175#c52">Comment # 52</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu.dc=1 shows performance issues with Xorg compositors when moving windows" href="https://bugs.freedesktop.org/show_bug.cgi?id=106175">bug 106175</a> from <a class="email" href="mailto:bearoso@gmail.com" title="Brandon Wright <bearoso@gmail.com>"> Brandon Wright</a> <pre>Ok, I think I understand what's going on. Forgive me if this sounds stupid, I'm looking at the DRM code for the first time. The old KMS interface uses what's flagged as "legacy" cursor updates. These are "asynchronous" in that they're handled and passed to the hardware as they come in. On the vertical retrace interrupt, it uses whatever the last data passed in was. My theory is the DC interface isn't passing these on to the hardware immediately. It's aggregating them until the next sync, when they're all handled at once. And that is what's causing the disturbance at page-flip time. High-report-rate mice might exacerbate it. Intel's driver hasn't merged that async code yet. It's still using legacy cursor updates and working around this. The DC code seems to have a TODO comment in amdgpu_dm.c that suggests something about the legacy_cursor_update flag, but it doesn't do anything with it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>