-
Notifications
You must be signed in to change notification settings - Fork 478
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change log for October 6, 2023 Vulkan 1.3.267 spec update:
Internal Issues * Detect old wording of boilerplate pname:pNext description in CI (internal issue 2186). * Clarify ename:VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT with regard to queue submission (internal issue 3627). * Update apiext:VK_NV_low_latency2 pname:pInfo pointers to be `const` (internal issue 3637). * Add slink:VkDescriptorSetLayoutBindingFlagsCreateInfo and slink:VkDescriptorSetAllocateInfo VUs for ename:VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT (internal MR 6127). * Consolidate VUs in `access_mask_2_common.adoc` (internal MR 6166). * Fix slink:VkGraphicsPipelineCreateInfo::pname:pColorBlendState->attachmentCount VU to apply only when the blend state is not dynamic (internal MR 6171). * Add missing object types to the <<debugging-object-types, VkObjectType and Vulkan Handle Relationship>> table (internal MR 6175). * Fix typo ("`Non-private`" -> "`Private`") in the description of <<memory-model-non-private, private memory operations obeying program order>> (internal MR 6176). * Add reflow test for list continuation in VUs (internal MR 6177). * Correct type of flink:vkQueueNotifyOutOfBandNV::pname:pQueueTypeInfo (internal MR 6179). * Add XML `len` attribute for slink:VkFrameBoundaryEXT::pname:pTag order>> (internal MR 6180). * Consolidate VUs for apiext:VK_ANDROID_external_format_resolve (internal MR 6183). * Upstream Vulkan SC 1.0.13 changes to this repository (internal vulkansc issue 179). New Extensions * apiext:VK_EXT_nested_command_buffer * apiext:VK_NV_extended_sparse_address_space
- Loading branch information
Showing
29 changed files
with
816 additions
and
202 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
// Copyright 2023 The Khronos Group, Inc | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_EXT_nested_command_buffer.adoc[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2023-09-18 | ||
*Contributors*:: | ||
- Daniel Story, Nintendo | ||
- Peter Kohaut, NVIDIA | ||
- Shahbaz Youssefi, Google | ||
- Slawomir Grajewski, Intel | ||
- Stu Smith, AMD | ||
|
||
=== Description | ||
|
||
With core Vulkan it is not legal to call flink:vkCmdExecuteCommands when | ||
recording a secondary command buffer. | ||
This extension relaxes that restriction, allowing secondary command buffers | ||
to execute other secondary command buffers. | ||
|
||
include::{generated}/interfaces/VK_EXT_nested_command_buffer.adoc[] | ||
|
||
=== Issues | ||
|
||
1) The Command Buffer Levels property for the Vulkan commands comes from the | ||
`cmdbufferlevel` attribute in `vk.xml` for the command, and it is currently | ||
not possible to modify this attribute based on whether an extension is | ||
enabled. | ||
For this extension we want the `cmdbufferlevel` attribute for | ||
vkCmdExecuteCommands to be `primary,secondary` when this extension is | ||
enabled and `primary` otherwise. | ||
|
||
*RESOLVED*: The `cmdbufferlevel` attribute for flink:vkCmdExecuteCommands | ||
has been changed to `primary,secondary` and a new VUID added to prohibit | ||
recording this command in a secondary command buffer unless this extension | ||
is enabled. | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2023-09-18 (Piers Daniell) | ||
** Internal revisions |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
// Copyright (c) 2023 NVIDIA Corporation | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_NV_extended_sparse_address_space.adoc[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2023-10-03 | ||
*Contributors*:: | ||
- Russell Chou, NVIDIA | ||
- Christoph Kubisch, NVIDIA | ||
- Eric Werness, NVIDIA | ||
- Jeff Bolz, NVIDIA | ||
|
||
=== Description | ||
|
||
Implementations may be able to support an extended address space for sparse | ||
memory resources, but only for a certain set of usages. | ||
|
||
This extension adds a query for the extended limit, and the supported usages | ||
that are allowed for that limit. | ||
This limit is an increase to | ||
slink:VkPhysicalDeviceLimits::pname:sparseAddressSpaceSize when the | ||
slink:VkImage or slink:VkBuffer uses only usages that are supported. | ||
|
||
include::{generated}/interfaces/VK_NV_extended_sparse_address_space.adoc[] | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2023-10-03 (Russell Chou) | ||
** Initial draft |
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.