PFND3D11DDI_CHECKDEFERREDCONTEXTHANDLESIZES - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D11DDI_CHECKDEFERREDCONTEXTHANDLESIZES Pfnd3d11ddiCheckdeferredcontexthandlesizes;
VOID Pfnd3d11ddiCheckdeferredcontexthandlesizes(
D3D10DDI_HDEVICE unnamedParam1,
UINT *pHSizes,
D3D11DDI_HANDLESIZE *unnamedParam3
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The CheckDeferredContextHandleSizes function verifies the sizes of the driver-private memory spaces that hold the handle data of deferred context handles.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
pHSizesThe size, in bytes, of the array pointed to by pHandleSize.
unnamedParam3pHandleSize [out, optional]
An array of D3D11DDI_HANDLESIZE structures that describe the handle data of deferred context handles.
The driver can use the pfnSetErrorCb callback function to set a critical error code.
The driver is only required to implement CheckDeferredContextHandleSizes if the driver supports the D3D11DDICAPS_COMMANDLISTS_BUILD_2 capability that can be returned in the D3D11DDI_THREADING_CAPS structure from a call to the GetCaps(D3D10_2) function.
For more information about how CheckDeferredContextHandleSizes is used, see Using Context-Local DDI Handles.
The driver's CheckDeferredContextHandleSizes function cannot call the pfnSetErrorCb callback function to set the D3DDDIERR_DEVICEREMOVED error code because CheckDeferredContextHandleSizes is a capability-check type of function. The driver must ensure that it has enough information after device creation to respond to a call to CheckDeferredContextHandleSizes, even in the presence of D3DDDIERR_DEVICEREMOVED.
CheckDeferredContextHandleSizes should not encounter any errors. However, CheckDeferredContextHandleSizes might call pfnSetErrorCb for critical errors.
CheckDeferredContextHandleSizes