PFND3D10DDI_RESOURCEISSTAGINGBUSY - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D10DDI_RESOURCEISSTAGINGBUSY Pfnd3d10ddiResourceisstagingbusy;
BOOL Pfnd3d10ddiResourceisstagingbusy(
D3D10DDI_HDEVICE unnamedParam1,
D3D10DDI_HRESOURCE unnamedParam2
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The ResourceIsStagingBusy function determines whether a resource is currently being used by the graphics pipeline.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2hResource [in]
A handle to the resource.
ResourceIsStagingBusy returns a Boolean value that specifies whether the resource that the hResource parameter specifies is currently being used by the graphics pipeline. TRUE indicates that the graphics pipeline currently uses the resource; FALSE indicates that the graphics pipeline currently does not use the resource.
The Microsoft Direct3D runtime call to ResourceIsStagingBusy is roughly equivalent to the call to the ResourceMap function with the D3D10_DDI_MAP_FLAG_DONOTWAIT flag set in the Flags parameter, except that ResourceMap can perform only one subresource at a time and ResourceIsStagingBusy can be called while some of the subresources are currently mapped.
The user-mode display driver is not required to flush any partially built command buffer. If the driver is resident in the partially built command buffer, the driver qualifies as busy.
ResourceIsStagingBusy should not encounter any errors. However, ResourceIsStagingBusy might call the pfnSetErrorCb function for critical errors.