From 7cbdb8e667b5d099479b12e460ab97a11a69e39b Mon Sep 17 00:00:00 2001 From: Hans-Kristian Arntzen Date: Sun, 10 May 2026 17:49:19 +0200 Subject: [PATCH] wsi/common: Report correct time domain in VkPresentTimingInfo. During development of EXT_present_timing feature, we had to change from CLOCK_MONOTONIC time domain to PRESENT_STAGE_LOCAL_EXT, and that is the only domain reported to applications as being supported. This case was missed when reporting the timestamps, where applications can now get confused because we report the "actual" present timing domain instead of PRESENT_STAGE_LOCAL_EXT as would be expected. At the time, VVL didn't seem to catch this error in bringup-tests, but it does now. The only known impact is some goofyness in VVL, but it's possible that some application would have been broken by this bug. Signed-off-by: Hans-Kristian Arntzen Fixes: 47d69664d8f ("vulkan/wsi: Add common infrastructure for EXT_present_timing.") Reviewed-by: Mike Blumenkrantz Part-of: --- src/vulkan/wsi/wsi_common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vulkan/wsi/wsi_common.c b/src/vulkan/wsi/wsi_common.c index abbe514b9d2..55d29b068cf 100644 --- a/src/vulkan/wsi/wsi_common.c +++ b/src/vulkan/wsi/wsi_common.c @@ -1676,7 +1676,7 @@ wsi_GetPastPresentationTimingEXT( vk_outarray_append_typed(VkPastPresentationTimingEXT, &timings, timing) { timing->targetTime = swapchain->present_timing.timings[i].target_time; timing->presentId = in_timing->present_id; - timing->timeDomain = swapchain->present_timing.time_domain; + timing->timeDomain = VK_TIME_DOMAIN_PRESENT_STAGE_LOCAL_EXT; timing->timeDomainId = 0; timing->reportComplete = in_timing->complete;