The problem is not that *some* monotonic counter is needed, it is that we can only implement the extension with the host provided monotonic counters that match the same clock source used on the CPU side. On Windows the only clock source is `VK_TIME_DOMAIN_QUERY_PERFORMANCE_COUNTER_EXT`, on Linux the only clock sources are `VK_TIME_DOMAIN_CLOCK_MONOTONIC_RAW_EXT` and `VK_TIME_DOMAIN_CLOCK_MONOTONIC_EXT`. The clock source used for QPC need to match the one returned here, so that what we return as `VK_TIME_DOMAIN_QUERY_PERFORMANCE_COUNTER_EXT` is correct. This was correct before, but it's been broken since QPC was changed to use CLOCK_BOOTTIME. Even if QPC is now implemented in a more correct way wrt suspend time, it broke the Vulkan side, and this is technically a regression. There's apparently no way to have both unless Vulkan adds a CLOCK_BOOTTIME domain, and it should be added before we can consider switching both QPC and Vulkan to CLOCK_BOOTIME. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9866#note_126631