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

This reverts commit b6ab076d6b.

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.
This commit is contained in:
Jason Ekstrand 2015-05-18 20:22:51 -07:00
parent 923691c70d
commit 7c9f209427

View file

@ -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)