From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38800] glXSwapBuffersMscOML is slow on AMD Fusion but not on Intel 945 w/Atom
Date: Wed, 6 Jul 2011 20:07:59 -0700 (PDT) [thread overview]
Message-ID: <20110707030759.0A94513004D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-38800-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=38800
--- Comment #28 from Alex Deucher <agd5f@yahoo.com> 2011-07-06 20:07:58 PDT ---
(In reply to comment #27)
> (In reply to comment #22)
> > FWIW, the pageflip interrupts weren't too reliable at least on 6xx, but they
> > seemed to work ok on 7xx+.
>
> Thanks for the info Alex. Can you define "work ok"? Is this "no apparent
> problems, but only lightly tested" or more like "works nine out of ten times"?
>
No apparent problems, but only lightly tested.
> > Also, I can see problems where you might not get
> > interrupts for some flips if a later base update write comes in via the CP
> > before the irq handler has acked the interrupt from the frame before it.
>
> When would this happen? During or close to a mode-set? Not during normal page
> flipping, no? I thought that so far all crtc updates go directly via mmio
> instead of the CP? Or does Atombios use the CP?
>
All current pageflipping and modesetting happens via MMIO. I'm not even sure
it's a problem, just thinking out loud.
> >FWIW, I asked internally and the closed driver uses vblanks.
>
> Ok, that's a bit scary. Do you know if it is because it is supposed to be "good
> enough" or due to some real problems? I do know that the Catalyst drivers were
> far from perfect wrt. vsync'ed swapping in the past. My own toolkit implements
> a couple of crazy workarounds for some oddities i saw at least on Windows and
> OS/X, can't remember if it was on Linux as well. So from my experience i'm not
> sure if i personally would count that as a pro or contra argument against using
> something else than vblank irq's ;-)
I think it was mostly due to using the same well tested code across generations
since pre-r6xx asics didn't have the flip interrupts. Things might have
changed since I last asked months ago. I can check again. I'm assuming the
flip interrupts were added for a reason...
>
> At least evergreen seems to also have vline interrupts? One could (ab)use them
> as well to fake a home-grown pageflip completion interrupt, e.g., by triggering
> one at scanline 1, immediately after end of vblank and then just checking in
> the vline irq if the update_pending bit is clear -> pageflip completed.
All asics support vline interrupts.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-07-07 3:07 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 10:48 [Bug 38800] New: glXSwapBuffersMscOML is slow on AMD Fusion but not on Intel 945 w/Atom bugzilla-daemon
2011-06-30 10:53 ` [Bug 38800] " bugzilla-daemon
2011-06-30 10:53 ` bugzilla-daemon
2011-06-30 10:54 ` [Bug 38800] New: " Simon Farnsworth
2011-06-30 12:20 ` [Bug 38800] " bugzilla-daemon
2011-06-30 15:09 ` bugzilla-daemon
2011-06-30 17:10 ` bugzilla-daemon
2011-07-01 16:54 ` bugzilla-daemon
2011-07-01 16:57 ` bugzilla-daemon
2011-07-04 11:22 ` bugzilla-daemon
2011-07-04 13:27 ` bugzilla-daemon
2011-07-04 16:19 ` bugzilla-daemon
2011-07-04 16:30 ` bugzilla-daemon
2011-07-05 12:18 ` bugzilla-daemon
2011-07-05 12:24 ` bugzilla-daemon
2011-07-05 16:01 ` bugzilla-daemon
2011-07-05 16:56 ` bugzilla-daemon
2011-07-05 17:37 ` bugzilla-daemon
2011-07-05 17:57 ` bugzilla-daemon
2011-07-06 10:15 ` bugzilla-daemon
2011-07-06 10:19 ` bugzilla-daemon
2011-07-06 14:24 ` bugzilla-daemon
2011-07-06 20:54 ` bugzilla-daemon
2011-07-06 21:13 ` bugzilla-daemon
2011-07-06 21:25 ` bugzilla-daemon
2011-07-06 21:35 ` bugzilla-daemon
2011-07-06 21:52 ` bugzilla-daemon
2011-07-07 1:02 ` bugzilla-daemon
2011-07-07 1:43 ` bugzilla-daemon
2011-07-07 3:07 ` bugzilla-daemon [this message]
2011-07-07 8:47 ` bugzilla-daemon
2011-07-07 13:36 ` bugzilla-daemon
2011-07-07 13:49 ` bugzilla-daemon
2011-07-07 14:11 ` bugzilla-daemon
2011-07-07 17:46 ` bugzilla-daemon
2011-07-07 19:06 ` bugzilla-daemon
2011-07-07 20:39 ` bugzilla-daemon
2011-07-07 21:06 ` bugzilla-daemon
2011-07-07 21:25 ` bugzilla-daemon
2011-07-07 21:51 ` bugzilla-daemon
2011-07-08 9:41 ` bugzilla-daemon
2011-07-08 10:05 ` bugzilla-daemon
2011-07-08 11:32 ` bugzilla-daemon
2011-07-08 12:18 ` bugzilla-daemon
2011-07-08 14:12 ` bugzilla-daemon
2011-07-08 14:17 ` bugzilla-daemon
2011-07-08 14:20 ` bugzilla-daemon
2011-07-08 14:22 ` bugzilla-daemon
2011-07-08 14:25 ` bugzilla-daemon
2011-07-08 14:51 ` bugzilla-daemon
2011-07-08 18:16 ` bugzilla-daemon
2011-07-08 18:21 ` bugzilla-daemon
2011-07-11 21:28 ` bugzilla-daemon
2011-07-14 21:19 ` 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=20110707030759.0A94513004D@annarchy.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