<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [awesomenauts][radeonsi] pageflip is clearly missing vblank with vsync on" href="https://bugs.freedesktop.org/show_bug.cgi?id=79850#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [awesomenauts][radeonsi] pageflip is clearly missing vblank with vsync on" href="https://bugs.freedesktop.org/show_bug.cgi?id=79850">bug 79850</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to <a href="show_bug.cgi?id=79850#c21">comment #21</a>) > It would mean the pixmap transformation is costing too much in time > regarding vblank time, making happen the swap in the middle of the visible > screen. When the window pixmap is not the screen pixmap, a GLX/DRI2 buffer swap involves two copies: one from the DRI2 back buffer to the window pixmap, and one from the window pixmap to the screen pixmap. It's unrealistic for the second copy to finish before the end of the vertical blank period, resulting in the visible tearing. (In reply to <a href="show_bug.cgi?id=79850#c22">comment #22</a>) > - I did swap my TAHITI XT (7970) with a JUNIPER PRO (5750), the pixmap > transformation seems GPU bound since the tearing appears quite lower on > JUNIPER PRO than with TAHITI XT. Could be due to EXA vs. glamor. In the latter case, the copies described above are rasterized as two triangles each, which makes the tearing more noticeable.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>