Lines Matching refs:physical
11 [open,refpage='VkPhysicalDevice',desc='Opaque handle to a physical device object',type='handles']
14 A physical device usually represents a single complete implementation of
26 [[devsandqueues-physical-device-enumeration]]
29 [open,refpage='vkEnumeratePhysicalDevices',desc='Enumerates the physical devices accessible to a Vu…
31 To retrieve a list of physical device objects representing the physical
39 number of physical devices available or queried, as described below.
43 If pname:pPhysicalDevices is `NULL`, then the number of physical devices
49 If pname:pPhysicalDeviceCount is less than the number of physical devices
52 indicate that not all the available physical devices were returned.
57 [open,refpage='vkGetPhysicalDeviceProperties',desc='Returns properties of a physical device',type='…
59 To query general properties of physical devices once enumerated, call:
63 * pname:physicalDevice is the handle to the physical device whose
71 [open,refpage='VkPhysicalDeviceProperties',desc='Structure specifying physical device properties',t…
81 the physical device.
82 * pname:deviceID is a unique identifier for the physical device among
92 device-specific limits of the physical device.
95 structure specifying various sparse related properties of the physical
179 The same device ID should: be used for all physical implementations of that
209 [open,refpage='VK_MAX_PHYSICAL_DEVICE_NAME_SIZE',desc='Length of a physical device name string',typ…
212 an array containing a physical device name string, as returned in
218 [open,refpage='VkPhysicalDeviceType',desc='Supported physical device types',type='enums']
220 The physical device types which may: be returned in
236 The physical device type is advertised for informational purposes only, and
243 [open,refpage='vkGetPhysicalDeviceProperties2',desc='Returns properties of a physical device',type=…
245 To query general properties of physical devices once enumerated, call:
257 * pname:physicalDevice is the handle to the physical device whose
271 [open,refpage='VkPhysicalDeviceProperties2',desc='Structure specifying physical device properties',…
287 describing properties of the physical device.
298 [open,refpage='VkPhysicalDeviceVulkan11Properties',desc='Structure specifying physical device prope…
312 pname:subgroupSize is at least 1 if any of the physical device's queues
321 ename:VK_SHADER_STAGE_COMPUTE_BIT bit set if any of the physical
328 ename:VK_SUBGROUP_FEATURE_BASIC_BIT bit set if any of the physical
356 [open,refpage='VkPhysicalDeviceVulkan12Properties',desc='Structure specifying physical device prope…
409 implementation will perform dynamic host memory allocations for physical
502 [open,refpage='VkPhysicalDeviceVulkan13Properties',desc='Structure specifying physical device prope…
540 [open,refpage='VkPhysicalDeviceIDProperties',desc='Structure specifying IDs related to the physical…
718 * pname:driverID is a unique identifier for the driver of the physical
733 These are properties of the driver corresponding to a physical device.
769 [open,refpage='VK_MAX_DRIVER_NAME_SIZE',desc='Maximum length of a physical device driver name strin…
784 [open,refpage='VK_MAX_DRIVER_INFO_SIZE',desc='Length of a physical device driver information string…
823 …sInfoPropertiesEXT',desc='Structure containing PCI bus information of a physical device',type='str…
840 These are properties of the PCI bus information of a physical device.
847 …DeviceDrmPropertiesEXT',desc='Structure containing DRM information of a physical device',type='str…
856 * pname:hasPrimary is a boolean indicating whether the physical device has
858 * pname:hasRender is a boolean indicating whether the physical device has
868 These are properties of the DRM information of a physical device.
876 …tructure containing information about integer dot product support for a physical device',type='str…
1050 a physical device.
1100 These are properties of the image processing information of a physical
1108 …',desc='Structure containing information about tile image support for a physical device',type='str…
1131 These are properties of the tile image information of a physical device.
1156 These are properties of the image processing2 information of a physical
1164 …SFT',desc='Structure containing information about driver layering for a physical device',type='str…
1179 These are properties of the driver layering information of a physical
1195 …rtiesARM',desc='Structure containing scheduling control properties of a physical device',type='str…
1203 specifies the specific scheduling controls that a physical device
1212 …lagBitsARM',desc='Bitmask specifying scheduling controls supported by a physical device',type='enu…
1236 …milyProperties',desc='Reports properties of the queues of the specified physical device',type='pro…
1238 To query properties of queues available on a physical device, call:
1242 * pname:physicalDevice is the handle to the physical device whose
1335 queried from the physical device.
1337 For physical device feature queries see the <<features, Features>> chapter.
1385 If the physical device supports the <<features-protectedMemory,
1391 operations, at least one queue family of at least one physical device
1397 physical device feature is supported, then at least one queue family of at
1398 least one physical device exposed by the implementation must: support
1426 …ilyProperties2',desc='Reports properties of the queues of the specified physical device',type='pro…
1428 To query properties of queues available on a physical device, call:
1440 * pname:physicalDevice is the handle to the physical device whose
1599 Device objects represent logical connections to physical devices.
1604 As described in <<devsandqueues-physical-device-enumeration,Physical
1605 Devices>>, a Vulkan application will first query for all physical devices in
1607 Each physical device can: then be queried for its capabilities, including
1609 Once an acceptable physical device is identified, an application will create
1611 The created logical device is then the primary interface to the physical
1614 How to enumerate the physical devices in a system and query those physical
1616 <<devsandqueues-physical-device-enumeration, Physical Device Enumeration>>
1621 A single logical device can: be created from multiple physical devices, if
1622 those physical devices belong to the same device group.
1623 A _device group_ is a set of physical devices that support accessing each
1625 on all the physical devices.
1628 a subset of the physical devices in a device group by passing the physical
1630 For two physical devices to be in the same device group, they must: support
1646 [open,refpage='vkEnumeratePhysicalDeviceGroups',desc='Enumerates groups of physical devices that ca…
1680 Every physical device must: be in exactly one device group.
1685 [open,refpage='VkPhysicalDeviceGroupProperties',desc='Structure specifying physical device group pr…
1700 * pname:physicalDeviceCount is the number of physical devices in the
1703 slink:VkPhysicalDevice handles representing all physical devices in the
1710 across all physical devices in the group.
1717 [open,refpage='VK_MAX_DEVICE_GROUP_SIZE',desc='Length of a physical device handle array',type='cons…
1720 slink:VkPhysicalDevice handle values representing all physical devices in a
1747 A logical device is created as a _connection_ to a physical device.
1754 <<devsandqueues-physical-device-enumeration, Physical Device
1800 Multiple logical devices can: be created from the same physical device.
1806 same physical device.
2163 [open,refpage='VkDeviceGroupDeviceCreateInfo',desc='Create a logical device from multiple physical …
2165 A logical device can: be created that connects to one or more physical
2183 * pname:pPhysicalDevices is a pointer to an array of physical device
2187 physical devices that the logical device represents.
2190 The order of the physical devices in the pname:pPhysicalDevices array
2191 determines the _device index_ of each physical device, with element [eq]#i#
2193 Certain commands and structures refer to one or more physical devices by
2200 In particular, the device index of that physical device is zero.
2843 corresponding physical device (sname:VkPhysicalDevice) may: be otherwise
2846 In some cases, the physical device may: also be lost, and attempting to
2850 If the physical device has not been lost, and a new logical device is
2851 successfully created from that physical device, it must: be in the non-lost
2857 Whilst logical device loss may: be recoverable, in the case of physical
2859 unless additional, unaffected physical devices exist on the system.
2864 In many cases, physical device loss may: cause other more serious issues
3022 As discussed in the <<devsandqueues-physical-device-enumeration,Physical
3029 family on that physical device.
3035 Grouping of queue families within a physical device is
3041 The general expectation is that a physical device groups all queues of
3044 physical device may: return two separate queue families with the same
3048 Once an application has identified a physical device with the queue(s) that
3489 by the underlying physical device, including synchronization with semaphores
3522 able to support the mapping of a virtual address to a physical address on