anv: Don't disable snooping for mempools
authorKristian Høgsberg Kristensen <kristian.h.kristensen@intel.com>
Fri, 29 Jan 2016 23:45:18 +0000 (15:45 -0800)
committerKristian Høgsberg Kristensen <kristian.h.kristensen@intel.com>
Sat, 30 Jan 2016 01:19:51 +0000 (17:19 -0800)
There's an intermittent flushing problem with VkEvent that we need to
root cause. For now, using the snooping feature keeps the memory pools
up to date with GPU writes and fixes the problem.

src/vulkan/anv_allocator.c

index 4be149ea695aa783eb185a30a9d6aa5966d09006..e935cd71df0d26b309d75cce41d3103b61868de2 100644 (file)
@@ -441,6 +441,7 @@ anv_block_pool_grow(struct anv_block_pool *pool, struct anv_block_state *state)
       goto fail;
    cleanup->gem_handle = gem_handle;
 
+#if 0
    /* Regular objects are created I915_CACHING_CACHED on LLC platforms and
     * I915_CACHING_NONE on non-LLC platforms. However, userptr objects are
     * always created as I915_CACHING_CACHED, which on non-LLC means
@@ -452,6 +453,7 @@ anv_block_pool_grow(struct anv_block_pool *pool, struct anv_block_state *state)
       anv_gem_set_domain(pool->device, gem_handle,
                          I915_GEM_DOMAIN_GTT, I915_GEM_DOMAIN_GTT);
    }
+#endif
 
    /* Now that we successfull allocated everything, we can write the new
     * values back into pool. */