Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vk protected content final #8258

Merged
merged 30 commits into from
Nov 12, 2024
Merged

Conversation

phoenixxxx
Copy link
Contributor

This is the last part of the protected contend feature:

  • Cache the render buffer in the render pass strucutre
  • Enable the proteded path in the Render Target
  • Make sure we build the protected version of the depth/color in the swap chaing
  • Minor cleanup/restrucuring of the code
phoenixxxx and others added 28 commits June 4, 2024 12:35
We needed to get the caching of the command buffer as well as building
protected version of the depth buffer in that swap chain path.
Pass the queue and the queue family index.
Forgot to add the protected memory flag.
Wrong variable.
Push constant and subpass.
Adding the blitter to the list of protected paths.
The Render target was not storing the protection level.
Removing some of the redundency.
We were overriding the render pass command buffer.
Wrong pointer being used.
@poweifeng poweifeng added the internal Issue/PR does not affect clients label Nov 8, 2024
@@ -151,7 +151,8 @@ void VulkanBlitter::resolve(VulkanAttachment dst, VulkanAttachment src) {
}
#endif

VulkanCommandBuffer& commands = mCommands->get();
VulkanCommandBuffer& commands = dst.texture->getIsProtected() ?
mCommands->getProtected() : mCommands->get();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

8 spaces here

@phoenixxxx
Copy link
Contributor Author

Feedback addressed.

@poweifeng poweifeng merged commit 0108d66 into google:main Nov 12, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Issue/PR does not affect clients
2 participants