Windows Display Driver Model

Материал из Википедии — свободной энциклопедии
Это старая версия этой страницы, сохранённая BPK (обсуждение | вклад) в 07:04, 25 июня 2010 (← Новая страница: «{{Редактирую|BPK 11:04, 25 июня 2010 (UTC)|25 июня 2010}} '''Windows Display Driver Model''' ('''WDDM''', также '''WVDDM''' ...»). Она может серьёзно отличаться от текущей версии.
(разн.) ← Предыдущая версия | Текущая версия (разн.) | Следующая версия → (разн.)
Перейти к навигации Перейти к поиску

Windows Display Driver Model (WDDM, также WVDDM в эпоху Vista) это архитектура графических драйверов для видеокарты под управлением Microsoft Windows начиная с Windows Vista.[1]

Она является заменой для архитектуры видеодрайверов Windows XP и нацелена на повышение производительности графики и новую функциональность.[1]

WDDM предоставляет функциональность, необходимую для отображения рабочего стола и приложений с помощью диспетчера рабочего стола - диспетчера составных окон, работающего поверх Direct3D. Она также поддерживает интерфейсы новой инфраструктуры DXGI (DirectX Graphics Infrastructure), необходимые для основных операций создания и управления устройством. Спецификация WDDM требует видеокарту, поддерживающую по меньшей мере Direct3D 9, и должна реализовывать интерфейсы до Direct3D 9 для совместимости со старыми приложениями Direct3D; по желанию она может реализовывать интерфейсы для Direct3D 10/10.1 и выше.

Возможности, привнесённые моделью WDDM

Драйверы WDDM открывают новые функциональные области, которые не предоставлялись на унифицированной основе более ранними моделями графических драйверов:

Виртуализованная видеопамять

В контексте графики виртуализация означает, что отдельные процессы (в пользовательском пространстве) не могут видеть память соседних процессов даже путём вставки фальшивых команд в командный поток. Драйверы WDDM позволяют виртуализовать видеопамять [2] , 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.[3] 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 [4]. 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[5], with the rest already WDDM capable. It also requires some other hardware features (causing, for example, SM 2.0-supporting hardware such as Intel GMA 900 to fail the WDDM certification [6]).

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.[7]. WDDM 1.1 does not have this limitation.[8]

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) [9][10] although Dual View [11] is still available.[12]

WDDM 1.1

Windows 7 supports major additions to WDDM tentatively known as WDDM 1.1; the details of this new version were unveiled at WinHEC 2008. New features include [5]:

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.[16][17]

WDDM 1.1, Direct3D 11, Direct2D and DirectWrite will also be 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.Ошибка: некорректно задана дата установки (исправьте через подстановку шаблона)

WDDM 1.1 drivers are backward compatible with WDDM 1.0 specification; both 1.0 and 1.1 drivers can be used in Windows Vista with or without the Platform Update.[5]

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. WDDM 2.0 and WDDM 2.1, which at that time were expected post-Vista[18] but on which Microsoft had not put an introduction date, would offer fine grain preemptive multitasking and would require a new generation of GPUs.[19][20]

References

  1. ↑ 1 2 3 Windows Vista Display Driver Model
  2. ↑ Graphics Memory Reporting in WDDM
  3. ↑ The role of the Windows Display Driver Model in the DWM
  4. ↑ Cross Process Resource Sharing
  5. ↑ 1 2 3 WHDC: Graphics Guide for Windows 7. Microsoft (12 июня 2009).
  6. ↑ Intel excuse for no GMA900 WDDM driver: no "HW Scheduler" no driver, Beyond3D, October 26, 2006.
  7. ↑ MultiMonitor Support and Windows Vista. Дата обращения: 20 октября 2007.
  8. ↑ Working With the Windows 7 Graphics Architecture: WinHEC 2008
  9. ↑ Are there Control Panel features that were available under Windows XP that are no longer available on Windows Vista?
  10. ↑ Stretched Desktop or Spanning Mode Not Available in Catalyst Control Center Under Windows Vista
  11. ↑ Description of DualView in Windows XP
  12. ↑ MultiMonitor Support and Windows Vista
  13. ↑ Windows DDK - GDI Hardware Acceleration. MSDN. Дата обращения: 14 июня 2009.
  14. ↑ Windows DDK - DXVA-HD DDI. MSDN. Дата обращения: 13 июня 2009.
  15. ↑ Windows DDK - Overlay DDI. MSDN. Дата обращения: 13 июня 2009.
  16. ↑ Greg Schechter's Blog: Redirecting GDI, DirectX, and WPF applications
  17. ↑ Engineering Windows 7 Graphics Performance
  18. ↑ WinHEC 2006: Display Driver Logistics And Testing
  19. ↑ WinHEC 2006: Windows Display Driver Model (WDDM) v2 And Beyond
  20. ↑ Dan Warne. Windows graphics system to be overhauled. APC Magazine (June 1, 2006). Дата обращения: 2 июня 2006.

Шаблон:Microsoft APIs Шаблон:Windows Components

Источник — https://ru.wikipedia.org/w/index.php?title=Windows_Display_Driver_Model&oldid=25701004