commit 5904ee3f58e31185d588c9568aad065a59f72b1e
author Shahbaz Youssefi <syoussefi@chromium.org> Fri Jan 25 11:15:16 2019 -0500
committer Commit Bot <commit-bot@chromium.org> Fri Jan 25 18:57:07 2019 +0000
tree 7808f5c98d192ffbf3c55eca9fe6e20c6f95304a
parent 59d756e530c5bf85cf0a91b1f5e6a1df90a7fa2b

Vulkan: Fix timestamp query units

Vulkan returns timestamps in cycles, which needs to be converted to
nanoseconds (by multiplying by limits.timestampPeriod) for GLES.

On NVidia, this multiplier seems to be 1 for a majority of their
hardware, while the timer has less and more varying granularity on AMD,
Intel and others.

Bug: angleproject:2885
Change-Id: I34e08ad386e06619170975039385ce35cab025a5
Reviewed-on: https://chromium-review.googlesource.com/c/1436835
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

src/libANGLE/renderer/vulkan/RendererVk.cpp

diff --git a/src/libANGLE/renderer/vulkan/RendererVk.cpp b/src/libANGLE/renderer/vulkan/RendererVk.cpp
index 912a0dd..4c85f98 100644
--- a/src/libANGLE/renderer/vulkan/RendererVk.cpp
+++ b/src/libANGLE/renderer/vulkan/RendererVk.cpp
@@ -1636,6 +1636,10 @@
 
     timestampQueryPool.get().freeQuery(context, &timestampQuery);
 
+    // Convert results to nanoseconds.
+    *timestampOut = static_cast<uint64_t>(
+        *timestampOut * static_cast<double>(mPhysicalDeviceProperties.limits.timestampPeriod));
+
     return angle::Result::Continue;
 }