-
Notifications
You must be signed in to change notification settings - Fork 127
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add fence delay options at capture time
Add two capture options: - Fence Query Delay - Fence Query Delay Unit When capturing with intent to replay on a "slow" platform, we may want to force the captured application to adopt a "slow platform behavior" - for example, not re-using some resources because we know that at replay time command buffers will take a lot longer to be executed. To emulate this, this commit implement the notion of "fence query delay". The idea is that when the captured application queries a `VkFence` using `vkGetFenceStatus` or `vkWaitForFences` with `timeout` set to `0`, we transmit the call to the driver, but if the fence is ready, we do not return `VK_SUCCESS` directly. Instead, we return `VK_NOT_READY` for "a certain amount of time" specified by the two capture options. By default this amount of time is `0 call`, which means no delay at all: we give to the application the result from the driver directly. This amount of time can be specified in number of `calls` or in number of `frames`. The unit (calls/frames) is specified by fence query delay unit, and the number by fence query delay. In addition, this commit also fixes the `--sgfs` and `--sgfr` options that were not parsed correctly, and the behavior of `vkGetFenceStatus` and `vkWaitForFences` at replay time to not "spam" `vkGetFenceStatus` if the call was successful at capture time but not at replay time. Change-Id: I9adff58c364b6a08fde2a95502e3b79152e1cbdf
- Loading branch information
1 parent
8f763b8
commit fc3e9e1
Showing
18 changed files
with
343 additions
and
56 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.