Commit f466eb51 by Chris Forbes

Advertise VK_PRESENT_MODE_MAILBOX_KHR

This is required by vkmark and various other workloads. The present mode handling is not really correct -- both our fifo and mailbox modes behave more like IMMEDIATE due to XPutImage etc being completely unthrottled Future changes will introduce proper present mode handling for the Xlib and Xcb WSI implementations. Bug: b/124265819 Change-Id: Ia71ff928848be9925ffb30a27fe6c35732b68590 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/39288 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com> Tested-by: 's avatarChris Forbes <chrisforbes@google.com>
parent c7a09685
...@@ -29,7 +29,13 @@ static const VkSurfaceFormatKHR surfaceFormats[] = ...@@ -29,7 +29,13 @@ static const VkSurfaceFormatKHR surfaceFormats[] =
static const VkPresentModeKHR presentModes[] = static const VkPresentModeKHR presentModes[] =
{ {
// FIXME(b/124265819): Make present modes behave correctly. Currently we use XPutImage
// with no synchronization, which behaves more like VK_PRESENT_MODE_IMMEDIATE_KHR. We
// should convert to using the Present extension, which allows us to request presentation
// at particular msc values. Will need a similar solution on Windows - possibly interact
// with DXGI directly.
VK_PRESENT_MODE_FIFO_KHR, VK_PRESENT_MODE_FIFO_KHR,
VK_PRESENT_MODE_MAILBOX_KHR,
}; };
} }
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment