On Tue, Mar 31, 2015 at 05:32:07PM +0100, Tomas Elf wrote:
On 19/03/2015 12:30, john.c.harri...@intel.com wrote:
From: John Harrison john.c.harri...@intel.com
In order to explcitly track all GPU work (and completely remove the
outstanding
lazy request), it is necessary to add extra
On Tue, Mar 31, 2015 at 05:32:07PM +0100, Tomas Elf wrote:
On 19/03/2015 12:30, john.c.harri...@intel.com wrote:
@@ -2361,12 +2362,14 @@ void __i915_add_request(struct intel_engine_cs *ring,
* is that the flush _must_ happen before the next request, no matter
* what.
*/
-
On 19/03/2015 12:30, john.c.harri...@intel.com wrote:
From: John Harrison john.c.harri...@intel.com
In order to explcitly track all GPU work (and completely remove the outstanding
lazy request), it is necessary to add extra i915_add_request() calls to various
places. Some of these do not need
From: John Harrison john.c.harri...@intel.com
In order to explcitly track all GPU work (and completely remove the outstanding
lazy request), it is necessary to add extra i915_add_request() calls to various
places. Some of these do not need the implicit cache flush done as part of the
standard
