[Mesa-dev] [PATCH v4 19/23] anv: Soft-pin client-allocated memory
Jason Ekstrand
jason at jlekstrand.net
Thu May 31 15:46:40 UTC 2018
Now that we've done all that refactoring, addresses are now being
directly written into surface states by ISL and BLORP whenever a BO is
pinned so there's really nothing to do besides enable it.
---
src/intel/vulkan/anv_device.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/intel/vulkan/anv_device.c b/src/intel/vulkan/anv_device.c
index 69de75c..8b44b1b 100644
--- a/src/intel/vulkan/anv_device.c
+++ b/src/intel/vulkan/anv_device.c
@@ -2051,6 +2051,9 @@ VkResult anv_AllocateMemory(
bo_flags |= EXEC_OBJECT_ASYNC;
}
+ if (pdevice->use_softpin)
+ bo_flags |= EXEC_OBJECT_PINNED;
+
const VkImportMemoryFdInfoKHR *fd_info =
vk_find_struct_const(pAllocateInfo->pNext, IMPORT_MEMORY_FD_INFO_KHR);
--
2.5.0.400.gff86faf
More information about the mesa-dev
mailing list