From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 79850] [awesomenauts][radeonsi] pageflip is clearly missing vblank with vsync on Date: Wed, 02 Jul 2014 05:52:18 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1999627443==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 5631A6E41C for ; Tue, 1 Jul 2014 22:52:18 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1999627443== Content-Type: multipart/alternative; boundary="1404280338.eab16aB0.27427"; charset="us-ascii" --1404280338.eab16aB0.27427 Date: Wed, 2 Jul 2014 05:52:18 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D79850 --- Comment #23 from Michel D=C3=A4nzer --- (In reply to comment #21) > 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, resultin= g in the visible tearing. (In reply to comment #22) > - 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 ab= ove are rasterized as two triangles each, which makes the tearing more noticeab= le. --=20 You are receiving this mail because: You are the assignee for the bug. --1404280338.eab16aB0.27427 Date: Wed, 2 Jul 2014 05:52:18 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 23 on bug 79850<= /a> from Michel D=C3=A4nzer
(In reply to comment #=
21)
> It would mean the pixmap transformation is costi=
ng too much in time
> regarding vblank time, making happen the swap in the middle of the vis=
ible
> 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, resultin=
g in
the visible tearing.


(In reply to comment #22)
>  - 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 ab=
ove
are rasterized as two triangles each, which makes the tearing more noticeab=
le.


You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1404280338.eab16aB0.27427-- --===============1999627443== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1999627443==--