Safe Haskell | None |
---|---|
Language | Haskell2010 |
Synopsis
- cmdSetCheckpointNV :: CommandBuffer -> ("checkpointMarker" ::: Ptr ()) -> IO ()
- getQueueCheckpointDataNV :: Queue -> IO ("checkpointData" ::: Vector CheckpointDataNV)
- data QueueFamilyCheckpointPropertiesNV = QueueFamilyCheckpointPropertiesNV {}
- data CheckpointDataNV = CheckpointDataNV {}
- type NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_SPEC_VERSION = 2
- pattern NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_SPEC_VERSION :: forall a. Integral a => a
- type NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_EXTENSION_NAME = "VK_NV_device_diagnostic_checkpoints"
- pattern NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a
Documentation
cmdSetCheckpointNV :: CommandBuffer -> ("checkpointMarker" ::: Ptr ()) -> IO () Source #
vkCmdSetCheckpointNV - insert diagnostic checkpoint in command stream
Parameters
CommandBuffer
is the command buffer that will receive the marker
pCheckpointMarker
is an opaque application-provided value that will be associated with the checkpoint.
Valid Usage (Implicit)
CommandBuffer
must be a validCommandBuffer
handle
CommandBuffer
must be in the recording state- The
CommandPool
thatCommandBuffer
was allocated from must support graphics, compute, or transfer operations
Host Synchronization
- Host access to the
CommandPool
thatCommandBuffer
was allocated from must be externally synchronized
Command Properties
'
Command Buffer Levels | Render Pass Scope | Supported Queue Types | Pipeline Type |
---|---|---|---|
Primary Secondary | Both | Graphics Compute Transfer |
See Also
getQueueCheckpointDataNV :: Queue -> IO ("checkpointData" ::: Vector CheckpointDataNV) Source #
vkGetQueueCheckpointDataNV - retrieve diagnostic checkpoint data
Parameters
pCheckpointDataCount
is a pointer to an integer related to the number of checkpoint markers available or queried, as described below.pCheckpointData
is eitherNULL
or a pointer to an array ofCheckpointDataNV
structures.
Description
If pCheckpointData
is NULL
, then the number of checkpoint markers
available is returned in pCheckpointDataCount
.
Otherwise, pCheckpointDataCount
must point to a variable set by the
user to the number of elements in the pCheckpointData
array, and on
return the variable is overwritten with the number of structures
actually written to pCheckpointData
.
If pCheckpointDataCount
is less than the number of checkpoint markers
available, at most pCheckpointDataCount
structures will be written.
Valid Usage
- The device that
Queue
belongs to must be in the lost state
Valid Usage (Implicit)
pCheckpointDataCount
must be a valid pointer to auint32_t
value- If the value referenced by
pCheckpointDataCount
is not0
, andpCheckpointData
is notNULL
,pCheckpointData
must be a valid pointer to an array ofpCheckpointDataCount
CheckpointDataNV
structures
See Also
data QueueFamilyCheckpointPropertiesNV Source #
VkQueueFamilyCheckpointPropertiesNV - return structure for queue family checkpoint info query
Valid Usage (Implicit)
See Also
QueueFamilyCheckpointPropertiesNV | |
|
Instances
data CheckpointDataNV Source #
VkCheckpointDataNV - return structure for command buffer checkpoint data
Valid Usage (Implicit)
Note that the stages at which a checkpoint marker can be executed are
implementation-defined and can be queried by calling
getPhysicalDeviceQueueFamilyProperties2
.
See Also
PipelineStageFlagBits
,
StructureType
,
getQueueCheckpointDataNV
CheckpointDataNV | |
|
Instances
pattern NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_SPEC_VERSION :: forall a. Integral a => a Source #
type NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_EXTENSION_NAME = "VK_NV_device_diagnostic_checkpoints" Source #
pattern NV_DEVICE_DIAGNOSTIC_CHECKPOINTS_EXTENSION_NAME :: forall a. (Eq a, IsString a) => a Source #