Bug 35196 - X seems to ignore Option "AccelMethod" "XAA" still using EXA
Summary: X seems to ignore Option "AccelMethod" "XAA" still using EXA
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Acceleration/XAA (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-10 22:57 UTC by Bodo Thiesen
Modified: 2011-03-11 10:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
The xorg.conf used for the test (1.85 KB, text/plain)
2011-03-10 22:57 UTC, Bodo Thiesen 		no flags Details
The Xorg.log file generated by the run (45.24 KB, text/plain)
2011-03-10 23:04 UTC, Bodo Thiesen 		no flags Details
View All

Description Bodo Thiesen 2011-03-10 22:57:26 UTC 
Created attachment 44338 [details]
The xorg.conf used for the test

In my attempts to fix my performance issues with my Radeon card, I did a test run of the X server using cmdline "valgrind --tool=callgrind /usr/bin/X.nosuid" to see, where the X server burns all those CPU cycles I see in top. The answer: In libexa.so: exa_unaccel.c. That's obvious, because if it were accellerated, I wouldn't have made the test run in the first place, what's not obvious: I explicitly asked the X server to use XAA (to test, whether that's better). It seems the X server is just ignoring that particular option alltogether.
Comment 1 Bodo Thiesen 2011-03-10 23:04:13 UTC 
Created attachment 44339 [details]
The Xorg.log file generated by the run
Comment 2 Michel Dänzer 2011-03-11 02:43:42 UTC 
"AccelMethod" is a driver option. The radeon driver can't support XAA with KMS.
Comment 3 Bodo Thiesen 2011-03-11 10:53:00 UTC 
Oh, didn't know (found many references to the options in forums and just tried them ...). How about writing a warning message in Xorg.log like "XAA is not supported when KMS is enabled - falling back to EXA"?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.