mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-15 16:28:04 +02:00
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 <post@arntzen-software.no>
Fixes: 47d69664d8 ("vulkan/wsi: Add common infrastructure for EXT_present_timing.")
Reviewed-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41465>
This commit is contained in:
parent
e7a035df65
commit
7cbdb8e667
1 changed files with 1 additions and 1 deletions
|
|
@ -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;
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue