Summary: | r600g makes kwin (ab)use 100% CPU | ||
---|---|---|---|
Product: | Mesa | Reporter: | Öyvind Saether <oyvinds> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | fredrik, jlp.bugs |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Öyvind Saether
2010-09-29 17:24:58 UTC
Unless the backtrace is the same all or at least most of the time, a profile from sysprof or oprofile would probably be more useful. I've used too much time trying to figure out how to run the oprofile, I recompiled the kernel with support for it and tried searching for some example of how to use it for hours. Could you please just tell me what commands to run in order to get any useful information from it? Profiling data confirms what the backtrace shows. It seems we take this path each time we use a texture after calling glXBindTexImageEXT. Can we have the profiling data attached to bug ? Btw sysprof is lot easier to use Looks like the problem is an unnecessary copy of the pixmap contents as part of glXBindTexImageEXT(). The fact that the copy is done in software just adds insult to injury, but really it should be possible to use the BO of the pixmap directly. |
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.