From: Jason Ekstrand <jason.ekstrand@intel.com>
Date: Tue, 19 May 2015 03:22:51 +0000 (-0700)
Subject: Revert "vk/allocator: Don't use memfd when valgrind is detected"
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7c9f20942770b562037804b07bfe596885f1f28a;p=mesa.git

Revert "vk/allocator: Don't use memfd when valgrind is detected"

This reverts commit b6ab076d6b7dd91ce0dda8741ba974b2402fa726.

It turns out setting USE_MEMFD to 0 is really bad because it means we can't
resize the pool.  Besides, valgrind SVN handles memfd so we really don't
need this fallback for valgrind anymore.
---

diff --git a/src/vulkan/allocator.c b/src/vulkan/allocator.c
index 11cdf398198..17d44423342 100644
--- a/src/vulkan/allocator.c
+++ b/src/vulkan/allocator.c
@@ -258,11 +258,7 @@ anv_block_pool_init_slave(struct anv_block_pool *pool,
  * without copying.  It breaks valgrind however, so we have a MAP_ANONYMOUS
  * path we can take for valgrind debugging. */
 
-#ifdef HAVE_VALGRIND
-#  define USE_MEMFD 0
-#else
-#  define USE_MEMFD 1
-#endif
+#define USE_MEMFD 1
 
 void
 anv_block_pool_finish(struct anv_block_pool *pool)