From 14b8d02130f2ea681911e3f714e78371c5724e47 Mon Sep 17 00:00:00 2001 From: Jose Maria Casanova Crespo Date: Sat, 16 May 2026 18:25:58 +0200 Subject: [PATCH] v3dv: assert timestamp pool BO is disjoint from dst buffer BO The two BOs come from distjoint allocation nowadays. So they would never share the BO handle. In case this becomes false in the future, the BO hanldes needs to be de-duped as happens with TFU submisions. Reviewed-by: Iago Toral Quiroga Part-of: --- src/broadcom/vulkan/v3dv_queue.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/broadcom/vulkan/v3dv_queue.c b/src/broadcom/vulkan/v3dv_queue.c index 6c001f6e8b8..4398ff01237 100644 --- a/src/broadcom/vulkan/v3dv_queue.c +++ b/src/broadcom/vulkan/v3dv_queue.c @@ -578,6 +578,10 @@ handle_copy_query_results_cpu_job(struct v3dv_queue *queue, uintptr_t *kperfmon_ids = NULL; if (info->pool->query_type == VK_QUERY_TYPE_TIMESTAMP) { + /* timestamp pool BO is V3DV-internal, never aliased by user BO. If + * that could happen we would need to dedupe them + */ + assert(bo->handle != info->pool->timestamp.bo->handle); submit.bo_handle_count = 2; bo_handles = (uint32_t *)