| Summary: |
X seems to ignore Option "AccelMethod" "XAA" still using EXA |
| Product: |
xorg
|
Reporter: |
Bodo Thiesen <bothie> |
| Component: |
Server/Acceleration/XAA | Assignee: |
Xorg Project Team <xorg-team> |
| Status: |
RESOLVED
NOTABUG
|
QA Contact: |
Xorg Project Team <xorg-team> |
| Severity: |
normal
|
|
|
| Priority: |
medium
|
|
|
| Version: |
unspecified | |
|
| Hardware: |
x86 (IA32) | |
|
| OS: |
Linux (All) | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
| Attachments: |
|
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.
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.