From: "Émeric Maschino" <emeric.maschino@gmail.com>
To: dri-devel@lists.sourceforge.net
Subject: Re: 3D OpenGL applications eat CPU ressources
Date: Sat, 6 Feb 2010 20:47:49 +0100 [thread overview]
Message-ID: <d72eeaf61002061147u7a022531o7f7e91047461027e@mail.gmail.com> (raw)
In-Reply-To: <20100204153511.GA1434@localhost.localdomain>
2010/2/4 Jerome Glisse <glisse@freedesktop.org>:
> IIRC old radeon drm doesn't have any thing to dump GPU command stream.
> Look at http://www.x.org/docs/AMD/R5xx_Acceleration_v1.4.pdf to see
> what radeon GPU stream command looks like (packet pm4 stuff). Note that
> dump GPU command stream can quickly eat Gigs of data and finding what
> is causing the lockup is then very cumberstone especialy as in your
> case it sounds like it's a timing issue. You might want to force your
> card into pci mode to see if it's agp related.
Yep, setting Option "BusType" "PCI" in /etc/X11/xorg.conf prevents
from GPU lockup.
A a side note, strace glxinfo and strace glxgears still give me read()
errors on /tmp/.X11-unix/X0, so they're probably not related to GPU
lockup.
Anyway, I don't know whether this is due to PCI mode or not, but
OpenGL performances, although there's no more GPU lockup, are poor.
And serious OpenGL applications, as simulated by the SPECviewperf test
suite, have very irregular frame rates. If I'm not mistaken, the
BusType option is specific to the radeon driver (or maybe other
drivers too)? I mean, it's not a X.org wide configuration option,
isn't it? This would thus narrow my investigation path to the AGP code
of the radeon driver, right?
Émeric
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
next prev parent reply other threads:[~2010-02-06 19:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 13:28 3D OpenGL applications eat CPU ressources Émeric Maschino
2010-01-31 16:42 ` Jerome Glisse
2010-02-01 21:17 ` Émeric Maschino
2010-02-01 22:00 ` Stephane Marchesin
2010-02-02 21:19 ` Émeric Maschino
2010-02-03 10:53 ` Stephane Marchesin
2010-02-04 14:37 ` Émeric Maschino
2010-02-04 15:35 ` Jerome Glisse
2010-02-06 19:47 ` Émeric Maschino [this message]
2010-02-06 20:04 ` Alex Deucher
2010-02-06 23:42 ` Dave Airlie
2010-02-07 18:17 ` Émeric Maschino
2010-02-07 0:45 ` Stephane Marchesin
2010-02-07 17:18 ` Émeric Maschino
2010-02-07 18:44 ` Émeric Maschino
2010-02-08 6:15 ` Alex Deucher
2010-02-08 20:24 ` Émeric Maschino
2010-02-11 20:25 ` Émeric Maschino
2010-02-16 22:37 ` Émeric Maschino
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=d72eeaf61002061147u7a022531o7f7e91047461027e@mail.gmail.com \
--to=emeric.maschino@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
/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.