From f28645f71cbe49099908dbdfd8c05ae3f8d051d6 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Kristian=20H=C3=B8gsberg=20Kristensen?= Date: Fri, 29 Jan 2016 15:45:18 -0800 Subject: [PATCH] anv: Don't disable snooping for mempools 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 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/vulkan/anv_allocator.c b/src/vulkan/anv_allocator.c index 4be149ea695..e935cd71df0 100644 --- a/src/vulkan/anv_allocator.c +++ b/src/vulkan/anv_allocator.c @@ -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. */ -- 2.30.2