Transcript Display Driver Logistics And Testing Nabeel Al-Kady Program Manager Graphics Platforms Unit Microsoft Corporation Overview Windows Display Driver Model (WDDM) Summary Current Progress Getting to RTM – areas of.

Display Driver
Logistics And Testing
Nabeel Al-Kady
Program Manager
Graphics Platforms Unit
Microsoft Corporation
Overview
Windows Display Driver Model (WDDM)
Summary
Current Progress
Getting to RTM – areas of focus
Stability
Performance
App-Compat
Media
Mobility
Post RTM planning
Pre-launch window
Advanced Scheduler
WDDM Summary
New display driver model for Windows Vista
The fundamental building block for DirectX and WinFX graphics APIs
Uses existing DX9 level hardware
Required for logo
Enables new scenarios
Desktop composition
Improved media playback
Improved monitor management
Virtualizes the GPU
Microsoft GPU memory manager and scheduler
Shares GPU resources among multiple applications
Increases stability
Simplifies driver interfaces
Moves driver code to user mode
Fault tolerant – allows recover from hangs
Improved diagnosability
Stability
Performance
WDDM Current Progress
Great collaboration with four major graphics vendors on inbox drivers
ATI
nVidia
Intel
S3
Broad support on desktops, mobile support rapidly increasing
On DX9 level hardware
WDDM is feature complete
Most IHV features also complete
Still several areas to concentrate on
Increased OEM engagement and Windows Vista testing
Stability – very large number of recovered hangs
Performance – more work required for Windows XP parity
AppCompat – many games are unplayable due to driver bugs
Media
Getting To RTM
Defining metrics
Goals have been defined for each critical area
Progress towards goals is measured by clearly defined metrics
Metrics can be calculated on a per-IHV basis
When all goals have been met, we are ready to ship
Goals
Stability – display drivers account for <10% of total system crashes
Performance – display drivers perform at Windows XP parity
AppCompat – 95% of Windows XP games are playable
Media – all key user scenarios work
Mobility – all mobile-specific scenarios work on targeted machines
WDK – all WDK tests must pass for logo’ability
Getting To RTM
Stability
Two metrics – OCA and CRASH
OCA
A score will be generated for each build publicly released
Score will be based on number of crashes for a particular driver
Score will be normalized by the market share of the driver
Market share is determined by crash data
Score will determine the percentage of total system crashes
due to a particular IHV driver
On machines with that particular IHV’s hardware
Still determining how to count recovered hangs
CRASH
Provides a weekly tracking index for display stability
Allows critical stability issues to be fixed before they impact customers
Getting To RTM
Performance
A weighted
performance
index was
created to
measure
overall graphics
performance
Dx9
70%
PerfX
25%
Fill Rate
4%
Geometry
4%
Bandwidth
4%
Overhead
5%
HLSL
6%
API
2%
DX9Apps
(FarCry, UT2004, Halo)
25%
3DMark2003
10%
3DMark2005
10%
Dx8
20%
PerfX2
6%
Fill Rate
2%
Geometry
2%
Bandwidth
2%
DX8Apps
8%
3DMark2001
6%
Dx7
5%
Half Life
2%
3DMark2000
3%
OpenGL
5%
Getting To RTM
AppCompat
Three tiers of games used for AppCompat
Tiers determined by age and sales of game
Tier 1 = 105 games
Tier 2 = 132 games
Focus is currently on Tier1 games, but Tier2 is next
IHV score = # passing games/(# passing games + #
of failing games due to IHV bugs)
This score does not penalize IHVs for OS bugs
However, if OS app bugs are fixed and IHV app bugs
are exposed, the score may decrease
Getting To RTM
Media
Key customer
scenarios
must work
IHV scores will
be based on the
number of
working scenarios
WMP
scenarios
HW features required
WMV
DXVA2 VP, WMV, VC1
WMDRM
WMV
DXVA2 VP, WMV, VC1,
PVP-OPM
A9 disc
DXVA2 VP, WMV, VC1,
PVP-OPM
DVD
DXVA2 VP, MPEG2
DVRMS
DXVA2 VP, MPEG2
DV-AVI
DXVA2 VP
MCE
scenarios
TV playback
DXVA2 VP, MPEG2,
COPP, TV-out
WMDRM
WMV
DXVA2 VP, WMV, VC1,
TV-out
DVD
DXVA2 VP, MPEG2,
Macrovision, TV-out
VMG
scenarios
DV-AVI
DXVA2 VP, TV-out
WMV
DXVA2 VP, WMV, VC1
Getting To RTM
Mobility
Mobile-specific features are very complex
Significant interaction of OS, IHV driver, and OEM BIOS
Request that OEMs help test these scenarios
Microsoft has tools and whitepapers to aid this process
Key mobile scenarios
Extend via display applet
Cloneview via hotkey switch
Rotation
TMM – Transient multimon manager
Hot Plug Detect (HPD)
Cloneview
Extend
External Only
Getting To RTM
WDK
WDK Feature complete now and available for evaluation
95%+ content complete for Display adapters/chipset program,
with most of the remaining content being DX10 tests
Ability to logo Windows Vista drivers starting from RC1
Major areas of focus for Display tests
WDDM functionality and conformance
D3D Conformance, with extra focus on WinFX, PIX and VMG scenarios
DXVA and EVR
OPM
General Stability (Invalid parameter, CRASH, FUS, Terminal services)
In addition, tests now for Mobile and Media Center specific scenarios
Post RTM Planning
Before launch
The window between RTM and launch will be critical
Extra time to fix driver bugs based on MS and OEM testing
Logo’d drivers should be uploaded to IHV websites and WU
Microsoft will continue to actively test new driver drops
and help to prioritize issues
This will insure a successful launch and
pre-install experience
Post RTM Planning
After launch
There will be a large influx of customer feedback
IHVs, OEMs, and Microsoft must be ready
to quickly respond
Familiarity with new Microsoft tools for stability,
reliability, and performance will be necessary
OCA bucketization
Diagnosability
Post RTM Planning
Diagnosability
Goal: Collect useful information in order to successfully
reproduce and diagnose GPU hangs
GPU recovery success: Debug report 0x117
GPU recovery failure: Bugcheck code 0x116
Data is collected as soon as the WDDM Scheduler detects a timeout
Unique minidump for each detected GPU timeout
Could have multiple Recoveries before a reboot
A snapshot of the internal state of the OS along with hardware and driver
information is taken in the minidump
Adapter, chipset and CPU identification
Video DMA buffer logs with process information
Video Scheduler preemption history
SBIOS information
Monitor mode settings
IHVs can use up to 128KB of data in minidump
for proprietary debugging information
Post RTM Planning
OCA Bucketization
Bucketization of non-hangs remains unchanged from Windows XP
IHVs write their own extensions to bucketize hangs based
on proprietary data
Improved bucketization based on hardware data collected
by the IHV and by Microsoft
Default bucketization
0x117_mydrv!Dispatch_CollectDbgInfo+0
New bucketization
0x117_mydrv!_TagA_TagB_TagC
0x117_mydrv!_ASIC_Process_GPURegisterTag
IHVs must supply their minidump extension dlls
Sample extension dll available
Post RTM Planning
WDDM V2.0 Overview
Post Windows Vista graphics technology
New generation of GPUs designed
for multi-tasking
Allows hardware level preemption
Hardware supports demand faulting
of resources
Still relies on some app cooperation
for efficient multi-tasking
Post RTM Planning
WDDM V2.1 Overview
Will ship simultaneously with WDDM 2.0
All features of WDDM V2.0 plus
Mid-pixel preemption
Doesn’t stall GPU on a page fault
True preemptive multi-tasking
Increased GPU Flexibility – GPU can
be used for any scenario without impact
to desktop experience
Call To Action
Continue to incorporate Windows Vista
into your mainline QA processes
More OEM involvement – let us know
your hot bugs so that we can fix them now!
Our work does not end with RTM
and Launch
Take advantage of the new Microsoft
provided tools to increase stability
Begin to plan for the development effort
of WDDM v2.x
Additional Resources
Web Resources
Specs: http://www.microsoft.com/whdc/device/display/default.mspx
Related Sessions
WDDM v2 and Beyond
Future Directions in Graphics
Desktop and Presentation Impact on Hardware Design
Feedback or questions? Email: Directx @ microsoft.com
Questions Or Feedback?
Send e-mail toDirectX @ microsoft.com
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.