From: Jason Ekstrand <jason.ekstrand@intel.com>
Date: Sat, 30 May 2015 04:15:47 +0000 (-0700)
Subject: vk/allocator: Don't call VALGRIND_MALLOCLIKE_BLOCK on fresh gem_mmap's
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=b2b9fc9fadb1afeae64357c76829a5afd9a0c758;p=mesa.git

vk/allocator: Don't call VALGRIND_MALLOCLIKE_BLOCK on fresh gem_mmap's
---

diff --git a/src/vulkan/allocator.c b/src/vulkan/allocator.c
index aeb08ce1cec..950b23c857a 100644
--- a/src/vulkan/allocator.c
+++ b/src/vulkan/allocator.c
@@ -700,7 +700,11 @@ anv_bo_pool_alloc(struct anv_bo_pool *pool, struct anv_bo *bo)
       return vk_error(VK_ERROR_MEMORY_MAP_FAILED);
    }
 
-   VG(VALGRIND_MALLOCLIKE_BLOCK(new_bo.map, pool->bo_size, 0, false));
+   /* We don't need to call VALGRIND_MALLOCLIKE_BLOCK here because valgrind
+    * already picks up on the gem_mmap and treats that as a malloc.  If we
+    * really want to be pedantic we could do a VALGRIND_FREELIKE_BLOCK
+    * right after the mmap, but there's no good reason.
+    */
 
    *bo = new_bo;
    return VK_SUCCESS;