Change EXA so that exaMoveOutPixmap() retains the framebuffer copy of the

pixmap, and damage is tracked so that a later exaMoveInPixmap won't
    result in an upload if no upload is necessary. This will likely improve
    the performance of the "Always" migration scheme significantly, and is
    a step in the path to more exact damage tracking between framebuffer
    and system memory.
This commit is contained in:
Eric Anholt 2006-03-16 18:43:55 +00:00
commit 14aafc258c
4 changed files with 276 additions and 167 deletions

View file

@ -1,3 +1,17 @@
2006-03-16 Eric Anholt <anholt@FreeBSD.org>
* exa/exa.c: (exaGetPixmapSize), (exaDestroyPixmap), (exaLog2),
(exaCreatePixmap):
* exa/exa_migration.c: (exaCopyDirtyToSys), (exaCopyDirtyToFb),
(exaPixmapSave), (exaMoveInPixmap), (exaMoveOutPixmap):
* exa/exa_priv.h:
Change EXA so that exaMoveOutPixmap() retains the framebuffer copy of
the pixmap, and damage is tracked so that a later exaMoveInPixmap won't
result in an upload if no upload is necessary. This will likely improve
the performance of the "Always" migration scheme significantly, and is
a step in the path to more exact damage tracking between framebuffer and
system memory.
2006-03-16 Daniel Stone <daniel@freedesktop.org>
* hw/xfree86/common/xf86PciInfo.h: