Display driver logistics and testing
1 / 22

Display Driver Logistics And Testing - PowerPoint PPT Presentation

  • Updated On :

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

Related searches for Display Driver Logistics And Testing

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Display Driver Logistics And Testing' - tanika

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Display driver logistics and testing l.jpg

Display DriverLogistics And Testing

Nabeel Al-KadyProgram ManagerGraphics Platforms UnitMicrosoft Corporation

Overview l.jpg

  • 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 l.jpg
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 l.jpg
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 l.jpg
Getting To RTMDefining 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 l.jpg
Getting To RTMStability

  • 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 crashesdue to a particular IHV driver

      • On machines with that particular IHV’s hardware

    • Still determining how to count recovered hangs


    • Provides a weekly tracking index for display stability

    • Allows critical stability issues to be fixed before they impact customers

Getting to rtm performance l.jpg
Getting To RTMPerformance

  • A weighted performanceindex wascreated to measureoverall graphics performance

Getting to rtm appcompat l.jpg
Getting To RTMAppCompat

  • 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 bugsare exposed, the score may decrease

Getting to rtm media l.jpg
Getting To RTMMedia

  • Key customer scenariosmust work

  • IHV scores willbe based on the number ofworking scenarios

Getting to rtm mobility l.jpg
Getting To RTMMobility

  • 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 l.jpg
Getting To RTMWDK

  • 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 l.jpg
Post RTM PlanningBefore 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 dropsand help to prioritize issues

  • This will insure a successful launch andpre-install experience

Post rtm planning after launch l.jpg
Post RTM PlanningAfter launch

  • There will be a large influx of customer feedback

  • IHVs, OEMs, and Microsoft must be readyto quickly respond

  • Familiarity with new Microsoft tools for stability, reliability, and performance will be necessary

    • OCA bucketization

    • Diagnosability

Post rtm planning diagnosability l.jpg
Post RTM PlanningDiagnosability

  • Goal: Collect useful information in order to successfullyreproduce 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 minidumpfor proprietary debugging information

Post rtm planning oca bucketization l.jpg
Post RTM PlanningOCA Bucketization

  • Bucketization of non-hangs remains unchanged from Windows XP

  • IHVs write their own extensions to bucketize hangs basedon proprietary data

  • Improved bucketization based on hardware data collectedby 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 l.jpg
Post RTM PlanningWDDM V2.0 Overview

  • Post Windows Vista graphics technology

  • New generation of GPUs designedfor multi-tasking

  • Allows hardware level preemption

  • Hardware supports demand faultingof resources

  • Still relies on some app cooperationfor efficient multi-tasking

Post rtm planning wddm v2 1 overview l.jpg
Post RTM PlanningWDDM 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 canbe used for any scenario without impactto desktop experience

Call to action l.jpg
Call To Action

  • Continue to incorporate Windows Vistainto your mainline QA processes

  • More OEM involvement – let us knowyour hot bugs so that we can fix them now!

  • Our work does not end with RTMand Launch

  • Take advantage of the new Microsoft provided tools to increase stability

  • Begin to plan for the development effortof WDDM v2.x

Additional resources l.jpg
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 l.jpg
Questions Or Feedback?

DirectX @ microsoft.com

  • Send e-mail to

Slide21 l.jpg

© 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.