On Sat, 10 Nov 2012 21:17:05 +0100, Daniel Vetter <daniel at ffwll.ch> wrote: > Hm, I've thought we could get away for the gpu activity tracking by > unconditionally assuming that any passed-in object is in is in all > read domains. For cache flushing it doesn't matter what we set anyway > since we invalidate/flush unconditionally all caches before/after each > batch. And for activity tracking we unconditionally put all objects in > a given execbuf to the front of the active list (with updated > ring/seqno). The only important thing is to keep the write tracking to > not break our various read/read optimizations. One overlooked aspect is that the domain tracking helps with debugging and identifying what the buffers are used for. It has paid dividends many times when reading error-states, and certainly will prove to be useful again in future. -Chris -- Chris Wilson, Intel Open Source Technology Centre
