diff options
author | Jason Ekstrand <[email protected]> | 2015-05-18 20:22:51 -0700 |
---|---|---|
committer | Jason Ekstrand <[email protected]> | 2015-05-18 20:57:43 -0700 |
commit | 7c9f20942770b562037804b07bfe596885f1f28a (patch) | |
tree | 62b566472a3a52b67235d6b1c708c7a50986f51b /src/vulkan | |
parent | 923691c70dc647ea6a10766f58d4f6d56b547c43 (diff) |
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.
Diffstat (limited to 'src/vulkan')
-rw-r--r-- | src/vulkan/allocator.c | 6 |
1 files changed, 1 insertions, 5 deletions
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) |