mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-08 15:38:09 +02:00
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:
parent
923691c70d
commit
7c9f209427
1 changed files with 1 additions and 5 deletions
|
|
@ -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)
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue