Windows Display Driver Model

Windows Display Driver Model (WDDM, also WVDDM (during the Vista time-frame) is the graphic driver architecture for video card drivers running Microsoft Windows versions beginning with Windows Vista. ^[1] It is a replacement for the Windows XP display driver architecture aimed at enabling better performance graphics and new graphics functionality. ^[1]

WDDM provides the functionality required to render the desktop and applications using Desktop Window Manager, a compositing window manager running on top of Direct3D. WDDM specifies the device driver interfaces required for Direct3D 10 and higher graphics. ^[2] The WDDM driver also implements the device driver interfaces for the Direct3D 9Ex runtime in order to run legacy Direct3D applications. Additionally, on Windows 7 or with the Platform Update for Windows Vista installed, WDDM includes a 10Level9 driver which can render Direct3D 10 applications using DirectX 9. The WDDM specification requires at least a Direct3D 9 (Shader Model 2.0) capable video card; it may optionally implement runtime interfaces for Direct3D 10/10.1 and higher.

On Windows Vista, the Desktop Window Manager renders Windows Aero using Direct3D 9.0Ex. On Windows 7, with WDDM 1.1 drivers, the Desktop Window Manager renders Aero using Direct3D 10 if the hardware supports Direct3D 10.^[3] If the graphics hardware only supports Direct3D 9, or in the absence of a WDDM 1.1 driver, the Desktop Window Manager in Windows 7 uses the DirectX 10 Level 9 driver to render Aero.^[3]

Features enabled by the WDDM

WDDM drivers enable new areas of functionality which were not uniformly provided by earlier display driver models. These include:

Virtualized video memory

In the context of graphics, virtualization means that individual processes (in userland) cannot see the memory of adjacent processes even by means of insertion of forged commands in the command stream. WDDM drivers allow video memory to be virtualized ^[4] , and video data to be paged out of video memory into system RAM. In case the video memory available turns out to be insufficient to store all the video data and textures, currently unused data is moved out to system RAM or to the disk. When the swapped out data is needed, it is fetched back. Virtualization could be supported on previous driver models (such as the XP Driver Model) to some extent, but was the responsibility of the driver, instead of being handled at the runtime level.

Scheduling

The runtime handles scheduling of concurrent graphics contexts. ^[5] Each list of commands is put in a queue for execution by the GPU, and it can be preempted by the runtime if a more critical task arrives and if it has not begun execution. This differs from native threads on the CPU where one task cannot be interrupted and therefore can take longer than necessary and make the computer appear less responsive. A hybrid scheduling algorithm between native and light threads with cooperation between the threads would achieve seamless parallelism. It is important to note that scheduling is not a new concept but it was previously the responsibility of individual driver developers. WDDM attempts to unify the experience across different vendors by controlling the execution of GPU tasks.

Cross-process sharing of Direct3D surfaces

A Direct3D graphics surface is the memory area that contains information about the textured meshes used for rendering a 2D or 3D scene. WDDM allows Direct3D surfaces to be shared across processes ^[6]. Thus, an application can incorporate a mesh created by another application into the scene it is rendering. Sharing textures between processes before WDDM was difficult, as it would have required copying the data from video memory to system memory and then back to video memory for the new device.

Enhanced fault-tolerance

If a WDDM driver hangs or encounters a fault, the graphics stack will restart the driver. ^[1] A graphics hardware fault will be intercepted and if necessary the driver will be reset. Drivers under Windows XP were free to deal with hardware faults as they saw fit either by reporting it to the user or by attempting to recover silently. With a WDDM driver, all hardware faults cause the driver to be reset and the user will be notified by a popup; this unifies the behavior across vendors.

Previous drivers were fully implemented in kernel mode, whereas WDDM is implemented partly in user mode. If the user mode area fails with an unrecoverable error, it will, at the most, cause the application to quit unexpectedly instead of producing a blue screen error as it would in previous driver models.

WDDM also allows the graphic hardware to be reset or unplugged without a proper reboot. In practice, a driver update should not necessitate a reboot.

Need for a new display driver model

One of the chief scenarios the Windows Display Driver Model enables is the Desktop Window Manager. Since the desktop and application windows managed by DWM are Direct3D applications, the number of open windows directly affects the amount of video memory required. Because there is no limit on the number of open windows, the video memory available may prove insufficient, necessitating virtualization. As the window contents that DWM composes into the final desktop are generated by different processes, cross-process surface sharing is necessary. Also, because there can be other DirectX applications running alongside DWM on the DWM-managed desktop, they must be able to access the GPU in a shared manner, necessitating scheduling.

Though this is true for Microsoft's implementation of a composited desktop under Windows Vista, on the other hand, a composited desktop need not theoretically require a new display driver model to work as expected. Successful implementations of composited desktops were done before Windows Vista on other platforms such as Quartz, Compiz, WindowFX). The approach Microsoft attempted was to try to make sure WDDM was a unified experience across different GPUs from multiple vendors by standardizing their features and performance. The software features missing from other driver models could be made immaterial by extensions or if a less restrictive or simply different driver model was in place.

Limitations

The new driver model requires the graphics hardware to have Shader Model 2.0 support at least (fixed function pipeline is now translated to 2.0 shaders). However, according to Microsoft, as of 2009, only about 1-2 percent of hardware used the XPDM^[3], with the rest already WDDM capable. Also, some other hardware features that were not previously enforced (causing, for example, SM 2.0-supporting hardware such as Intel GMA 900 to fail the WDDM certification ^[7]).

One of the limitations of WDDM driver model version 1.0 is that it does not support multiple drivers in a multi-adapter, multi-monitor setup. If a multi-monitor system has more than one graphics adapter powering the monitors, both the adaptors must use the same WDDM driver. If more than one driver is used, Windows will disable one of them.^[8]. WDDM 1.1 does not have this limitation. ^[9]

WDDM 1.0/1.1 does not allow some modes that were previously handled by the driver such as spanning mode (stretching the desktop across two monitors) ^{[10] [11]} although Dual View ^[12] is still available. ^[13]

WDDM 1.1

Windows 7 features WDDM v1.1; the details of this new version were unveiled at WinHEC 2008. New features include ^[3]

• DXGI 1.1. ^[2]
• With WDDM 1.1 drivers, DWM in Windows 7 can render using Direct3D 10 on Direct3D 10-capable hardware. On hardware which does not support Direct3D 10 and uses WDDM 1.0 drivers, DWM in Windows 7 can use Direct3D 10 Level 9. In contrast, DWM in Windows Vista is limited to using DirectX 9.0Ex. ^[3]
• Return of 2D GUI hardware acceleration for use by GDI ^[14] and Direct2D/DirectWrite
  • BitBlt, StretchBlt, TransparentBlt
  • AlphaBlend, ColorFill
  • ClearType font support
• Direct3D 11 Device Driver Interface (DDI)
• DXVA-HD DDI ^[15] WDDM 1.0 enabled DXVA 2.0.
• Hardware video overlay DDI ^[16]
• Optional AES 128 encryption
• Optional decoding of encrypted video content
• Support multiple drivers in a multi-adapter, multi-monitor setup

Hardware acceleration of GDI and Direct2D/DirectWrite operations helps reduce memory footprint in Windows 7, because DWM compositing engine no longer needs to keep a system memory copy of all surfaces used by GDI/GDI+, as in Windows Vista.^[17][18]

Support for Direct3D 11, Direct2D, DirectWrite, Direct3D 10Level9, WARP10, DXGI 1.1 is available with Windows Vista Platform Update; however GDI/GDI+ in Vista will continue to rely on software rendering and the Desktop Window Manager will continue to use Direct3D 9Ex to render Aero. Also, WDDM 1.1 drivers are backward compatible with or without the Platform Update; however they will function as WDDM 1.0 drivers on Windows Vista.^[3]

WDDM 1.0 drivers are forward compatible and can be used on Windows 7 however new functionality introduced in WDDM 1.1 won't be available.

Future versions

WDDM 2.0

At WinHEC 2006, Microsoft talked about how it was planning a major change to WDDM to allow for better multitasking on GPUs. According to Microsoft, WDDM 1.0 only allows rudimentary task scheduling with rendering "batch queue" granularity. In the future, WDDM 2.0 and WDDM 2.1, which were then expected post-Vista^[19] but on which Microsoft had not put an introduction date, would offer fine grain preemptive multitasking and would require a new generation of GPUs.^[20][21]

References

External links

• MSDN - WDDM Introduction
• List of GPUs supporting WDDM