Name

VK_KHR_zero_initialize_workgroup_memory - device extension

VK_KHR_zero_initialize_workgroup_memory

Name String

VK_KHR_zero_initialize_workgroup_memory

Extension Type

Device extension

Registered Extension Number

326

Revision

1

Ratification Status

Ratified

Extension and Version Dependencies

VK_KHR_get_physical_device_properties2

Deprecation State

• Promoted to Vulkan 1.3

Contact

• Alan Baker @alan-baker%0A*Here describe the issue or question you have about the VK_KHR_zero_initialize_workgroup_memory extension*

Other Extension Metadata

Last Modified Date

2020-11-18

Interactions and External Dependencies

• Promoted to Vulkan 1.3 Core

IP Status

No known IP claims.

Contributors

• Alan Baker, Google
• Jeff Bolz, Nvidia
• Faith Ekstrand, Intel

Description

This extension allows the use of a null constant initializer on shader Workgroup memory variables, allowing implementations to expose any special hardware or instructions they may have. Zero initialization is commonly used by applications running untrusted content (e.g. web browsers) as way of defeating memory-scraping attacks.

New Structures

• Extending PhysicalDeviceFeatures2, DeviceCreateInfo:

  • PhysicalDeviceZeroInitializeWorkgroupMemoryFeaturesKHR

New Enum Constants

• KHR_ZERO_INITIALIZE_WORKGROUP_MEMORY_EXTENSION_NAME

• KHR_ZERO_INITIALIZE_WORKGROUP_MEMORY_SPEC_VERSION

• Extending StructureType:

  • STRUCTURE_TYPE_PHYSICAL_DEVICE_ZERO_INITIALIZE_WORKGROUP_MEMORY_FEATURES_KHR

Promotion to Vulkan 1.3

Functionality in this extension is included in core Vulkan 1.3, with the KHR suffix omitted. The original type, enum and command names are still available as aliases of the core functionality.

Version History

• Revision 1, 2020-11-18 (Alan Baker)

  • Internal draft version

See Also

PhysicalDeviceZeroInitializeWorkgroupMemoryFeaturesKHR

Document Notes

For more information, see the Vulkan Specification

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.