Table of contents
TOC
Collapse the table of content
Expand the table of content

Supporting the DXGI DDI

Last Updated: 2/14/2017

To support the Microsoft DirectX Graphics Infrastructure (DXGI) device driver interface (DDI), the user-mode display driver must include the Dxgiddi.h header file. Dxgiddi.h also includes the Dxgitype.h header file, which contains definitions that are shared with application-level DXGI constructs. Dxgiddi.h defines several user-mode display driver entry points and a DXGI callback function that the driver can use to communicate with the kernel (including the display miniport driver).

The Microsoft Direct3D runtime supplies access to the DXGI DDI in the DXGI_DDI_BASE_ARGS structure that the DXGIBaseDDI member of the D3D10DDIARG_CREATEDEVICE structure points to in a call to the CreateDevice(D3D10) function. The user-mode display driver supplies pointers to these DXGI functions:

The driver implements these functions through members of the structures that the pDXGIDDIBaseFunctionsXxx members of DXGI_DDI_BASE_ARGS point to. The driver should record the pointer to the DXGI callback function table that the pDXGIBaseCallbacks member of DXGI_DDI_BASE_ARGS points to for later use. The driver should record the pointer to the DXGI callback function table rather than record the individual pointer to the DXGI callback function because the Direct3D runtime can change the address of the callback function whenever there is no thread inside the user-mode display driver. A further DXGI user-mode display driver requirement exists for software rasterizers. Such a user-mode display driver (more specifically, any driver that does not support hardware that is shared with the Direct3D version 9 DDI implementation on the graphics adapter) must return the DXGI_STATUS_NO_REDIRECTION value instead of the S_OK value from its CreateDevice(D3D10) function. Returning DXGI_STATUS_NO_REDIRECTION indicates to DXGI that it should not use the shared resource presentation path to effect communication with the Desktop Window Manager (DWM). The shared resource presentation path is created when calls to shared-resource functions (that is, CreateResource(D3D10) and OpenResource(D3D10) functions with the D3D10_DDI_RESOURCE_MISC_SHARED flag set) occur. However, DXGI should instead use techniques relevant to a swapchain whose buffers are available only to the CPU. For example, DXGI should move rendered data from the back buffer to the desktop by means other than the shared resource presentation path. In this situation, DXGI actually calls the driver's PresentDXGI function to move rendered data rather than effect communication with the DWM.

Send comments about this topic to Microsoft

© 2017 Microsoft