summaryrefslogtreecommitdiffstats
path: root/src/amd
diff options
context:
space:
mode:
authorSamuel Pitoiset <[email protected]>2018-06-21 14:39:28 +0200
committerSamuel Pitoiset <[email protected]>2018-06-22 17:47:06 +0200
commit07832083d37fc033c77fe2e431983947053e96fd (patch)
tree58494b4fc08de3fad70c216706ff03118f7b83a5 /src/amd
parent94bc06b1965fb8ac8a03bbd6c20314beea76d91e (diff)
radv: change the returned error in radv_signal_fence()
From my point of view, when we aren't able to submit a CS something terribly wrong happens and we are most likely going to lost the device. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Bas Nieuwenhuizen <[email protected]>
Diffstat (limited to 'src/amd')
-rw-r--r--src/amd/vulkan/radv_device.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index ffeb6450b33..3c63d8c86d6 100644
--- a/src/amd/vulkan/radv_device.c
+++ b/src/amd/vulkan/radv_device.c
@@ -2470,9 +2470,8 @@ static VkResult radv_signal_fence(struct radv_queue *queue,
false, fence->fence);
radv_free_sem_info(&sem_info);
- /* TODO: find a better error */
if (ret)
- return vk_error(queue->device->instance, VK_ERROR_OUT_OF_DEVICE_MEMORY);
+ return vk_error(queue->device->instance, VK_ERROR_DEVICE_LOST);
return VK_SUCCESS;
}