VkPhysicalDeviceMaintenance11FeaturesKHR(3)

# VkPhysicalDeviceMaintenance11FeaturesKHR(3) Manual Page

## Name

VkPhysicalDeviceMaintenance11FeaturesKHR - Structure describing whether the implementation supports maintenance11 functionality

## C Specification

The `VkPhysicalDeviceMaintenance11FeaturesKHR` structure is defined as:

    // Provided by VK_KHR_maintenance11
    typedef struct VkPhysicalDeviceMaintenance11FeaturesKHR {
        VkStructureType    sType;
        void*              pNext;
        VkBool32           maintenance11;
    } VkPhysicalDeviceMaintenance11FeaturesKHR;

## Members

This structure describes the following feature:

- `sType` is a VkStructureType value identifying this structure.

- `pNext` is `NULL` or a pointer to a structure extending this structure.

- `maintenance11` indicates that the implementation supports the following:

  - VK_IMAGE_CREATE_ALIAS_SINGLE_LAYER_DESCRIPTOR_BIT_KHR

  - The depth clipping state of the pipeline is well defined when the pipeline is created without VK_DYNAMIC_STATE_DEPTH_CLIP_ENABLE_EXT being set and the VkPipelineRasterizationDepthClipStateCreateInfoEXT structure is not present

  - VK_SHADER_CREATE_INDEPENDENT_SETS_BIT_KHR

  - Allow `queueFamilyIndexCount` of 1 in VkBufferCreateInfo, VkImageCreateInfo, VkPhysicalDeviceImageDrmFormatModifierInfoEXT, VkTensorCreateInfoARM when `sharingMode` is VK_SHARING_MODE_CONCURRENT

  - Require `minImageTransferGranularity` to be (1,1,1) even on transfer-only queues and add `optimalImageTransferGranularity` queue family property to communicate the performance bump for copies not aligned to the optimal granularity

  - When copying between a buffer and an image on a transfer-only queue, do not require `bufferOffset` to be a multiple of 4

## Description

If the `VkPhysicalDeviceMaintenance11FeaturesKHR` structure is included in the `pNext` chain of the VkPhysicalDeviceFeatures2 structure passed to vkGetPhysicalDeviceFeatures2, it is filled in to indicate whether each corresponding feature is supported. If the application wishes to use a VkDevice with any features described by `VkPhysicalDeviceMaintenance11FeaturesKHR`, it must add an instance of the structure, with the desired feature members set to VK_TRUE, to the `pNext` chain of VkDeviceCreateInfo when creating the VkDevice.

Valid Usage (Implicit)

- VUID-VkPhysicalDeviceMaintenance11FeaturesKHR-sType-sType
  `sType` must be VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAINTENANCE_11_FEATURES_KHR

Structure Chaining

Extends the structures

  - VkDeviceCreateInfo

  - VkPhysicalDeviceFeatures2

## See Also

VK_KHR_maintenance11, VkBool32, VkStructureType

## Document Notes

For more information, see the Vulkan Specification.

This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.

## Copyright

Copyright 2014-2026 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0