8754db77d8
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=24300 . Offscreen memory allocation can occur from various places, and apparently doing defragmentation from at least some of them can confuse some driver acceleration code. There's still the regular background defragmentation in the WakeupHandler, which should manage to keep fragmentation at a reasonable level. Signed-off-by: Michel Dänzer <daenzer@vmware.com> Signed-off-by: Keith Packard <keithp@keithp.com> |
||
|---|---|---|
| .. | ||
| exa_accel.c | ||
| exa_classic.c | ||
| exa_driver.c | ||
| exa_glyphs.c | ||
| exa_migration_classic.c | ||
| exa_migration_mixed.c | ||
| exa_mixed.c | ||
| exa_offscreen.c | ||
| exa_priv.h | ||
| exa_render.c | ||
| exa_unaccel.c | ||
| exa.c | ||
| exa.h | ||
| Makefile.am | ||