Skip to content

Add an interaction between KHR_maintenance11 and KHR_device_address_commands #2804

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.

Sign up for GitHub

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

Merged
oddhack merged 1 commit into from
Sep 4, 2026
Merged

Add an interaction between KHR_maintenance11 and KHR_device_address_commands #2804

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion chapters/commonvalidity/copy_image_device_memory_common.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,12 @@
pname:pCopyMemoryInfo->image must: not have been created with
ename:VK_IMAGE_CREATE_PROTECTED_BIT
* [[VUID-{refpage}-commandBuffer-13104]]
If the queue family used to create the slink:VkCommandPool which
If
ifdef::VK_KHR_maintenance11[]
the <<features-maintenance11,pname:maintenance11>> feature is not
enabled, and
endif::VK_KHR_maintenance11[]
the queue family used to create the slink:VkCommandPool which
pname:commandBuffer was allocated from does not support
ename:VK_QUEUE_GRAPHICS_BIT or ename:VK_QUEUE_COMPUTE_BIT, the
pname:addressRange.pname:address member of any element of
Expand Down