All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu,  7 Jul 2011 07:11:43 -0700 (PDT)	[thread overview]
Message-ID: <20110707141144.1397313004D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-38800-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=38800

--- Comment #32 from Jerome Glisse <glisse@freedesktop.org> 2011-07-07 07:11:43 PDT ---
Well i can think of similar bad case in the other way.

-wait for vblank
-wait for bo put us in next vblank
-program reg flip happen on this frame
-irq reporting report on next vblank

So we are off by one frame on the timestamp.

To me it seems more logic to first make sure that the potentialy longer wait
(bo_wait is unbound while vblank wait is bound for any human video mode) is
done first and then do the smaller one. Yes can we miss the next vblank but so
could we with bo wait after and with bo wait after we might do bad reporting on
the timestamp.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-07-07 14:11 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
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 [this message]
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=20110707141144.1397313004D@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.