From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79850] [awesomenauts][radeonsi] pageflip is clearly missing vblank with vsync on
Date: Wed, 02 Jul 2014 05:52:18 +0000 [thread overview]
Message-ID: <bug-79850-502-f3TBmUfgPF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79850-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1093 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79850
--- Comment #23 from Michel Dänzer <michel@daenzer.net> ---
(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, resulting 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 above
are rasterized as two triangles each, which makes the tearing more noticeable.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2090 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-07-02 5:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 20:36 [Bug 79850] New: [awesomenauts][radeonsi] pageflip is clearly missing vblank with vsync on bugzilla-daemon
2014-06-09 20:36 ` [Bug 79850] " bugzilla-daemon
2014-06-10 6:30 ` bugzilla-daemon
2014-06-10 17:13 ` bugzilla-daemon
2014-06-11 2:13 ` bugzilla-daemon
2014-06-11 16:43 ` bugzilla-daemon
2014-06-12 7:07 ` bugzilla-daemon
2014-06-13 15:18 ` bugzilla-daemon
2014-06-13 15:34 ` bugzilla-daemon
2014-06-13 16:03 ` bugzilla-daemon
2014-06-13 16:19 ` bugzilla-daemon
2014-06-16 8:01 ` bugzilla-daemon
2014-06-24 8:44 ` bugzilla-daemon
2014-06-24 14:35 ` bugzilla-daemon
2014-06-24 14:39 ` bugzilla-daemon
2014-06-24 16:33 ` bugzilla-daemon
2014-06-25 1:06 ` bugzilla-daemon
2014-06-25 12:50 ` bugzilla-daemon
2014-06-27 18:14 ` bugzilla-daemon
2014-06-29 23:10 ` bugzilla-daemon
2014-06-30 4:01 ` bugzilla-daemon
2014-07-01 14:53 ` bugzilla-daemon
2014-07-01 15:24 ` bugzilla-daemon
2014-07-02 5:52 ` bugzilla-daemon [this message]
2014-07-02 15:16 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-79850-502-f3TBmUfgPF@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).