diff options
| author | Samuel Pitoiset <[email protected]> | 2019-05-21 13:40:10 +0200 |
|---|---|---|
| committer | Samuel Pitoiset <[email protected]> | 2019-05-22 08:36:41 +0200 |
| commit | 32a0bc915a8d2ef2b94a3fd14296206046d01bba (patch) | |
| tree | d8edae77e7a7cc8acdb484c98937d2c428008199 /src | |
| parent | e9bfd88183a4d524ab9883d2caf7d75e1756f60f (diff) | |
radv: do not reset query pool during creation
From the Vulkan spec 1.1.108:
"After query pool creation, each query must be reset before
it is used."
So, the driver doesn't need to do this at creation time.
Signed-off-by: Samuel Pitoiset <[email protected]>
Reviewed-by: Bas Nieuwenhuizen <[email protected]>
Diffstat (limited to 'src')
| -rw-r--r-- | src/amd/vulkan/radv_query.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/amd/vulkan/radv_query.c b/src/amd/vulkan/radv_query.c index 63a2ab773a8..0bc7f8390b6 100644 --- a/src/amd/vulkan/radv_query.c +++ b/src/amd/vulkan/radv_query.c @@ -1035,8 +1035,6 @@ VkResult radv_CreateQueryPool( struct radv_query_pool *pool = vk_alloc2(&device->alloc, pAllocator, sizeof(*pool), 8, VK_SYSTEM_ALLOCATION_SCOPE_OBJECT); - uint32_t initial_value = pCreateInfo->queryType == VK_QUERY_TYPE_TIMESTAMP - ? TIMESTAMP_NOT_READY : 0; if (!pool) return vk_error(device->instance, VK_ERROR_OUT_OF_HOST_MEMORY); @@ -1082,7 +1080,6 @@ VkResult radv_CreateQueryPool( vk_free2(&device->alloc, pAllocator, pool); return vk_error(device->instance, VK_ERROR_OUT_OF_DEVICE_MEMORY); } - memset(pool->ptr, initial_value, pool->size); *pQueryPool = radv_query_pool_to_handle(pool); return VK_SUCCESS; |