On Sun, May 02, 2010 at 11:13:18AM -0700, Eric Anholt wrote:
> I've thought about writing this patch several times. Here's my concern.
> Say I drew to an FBO (render cache dirty) temporarily then freed it. It
> goes into the bo reuse list in userland, and is on the flushing list in
> kernel. Now
On Fri, 23 Apr 2010 14:32:39 +0200, Daniel Vetter
wrote:
> Reporting objects that are not currently used by the gpu but are
> dirty and not yet flushed creates havoc to libdrm's bo reuse:
> The usually immediatly following gtt_map afterwards will stall
> until the gpu has executed the writeback.
Reporting objects that are not currently used by the gpu but are
dirty and not yet flushed creates havoc to libdrm's bo reuse:
The usually immediatly following gtt_map afterwards will stall
until the gpu has executed the writeback.
v2: Fix refcount leak and missing unlock in the error path. Spotte
