Certifying graphics experiences on Windows 8 HW-215T Certifying graphics experiences on Windows 8 Rudolph Balaz Senior Program Manager Lead

Agenda Windows Hardware Certification Kit (HCK) for Graphics Key to delivering a great experience Scenario focused Testing Targeting key experiences User Experience Reliability and Stability Developer Experience Partner Experience Goals of this presentation Understanding how the Windows Hardware Certificate program helps our partners design a Windows 8 system Demonstrate how the requirements are easy to understand and provide direct value to the end user

Certified WDDM Graphics Drivers ensure devices are designed for a great Metro style user experience

Key to Delivering a great graphics experience Windows 8 is delivering a Metro style user experience Windows graphics driver model evolved and optimized for Metro style experiences on a variety of form factors Certification enables you to design to meet these expectations Experience / Metrics / Tools Key Metro style expectations for graphics: Graphics performance – End user experience Graphics quality – End user experience Graphics conformance – Developer confidence

Scenario focused testing Windows 8 graphics stack enables improved experiences System boot Login Usage scenarios such as - touch, animation, rotation and sleep Certification for graphics expanded End to end Scenario focused New tools and content – Performance test debut

Metro style experiences

Seamless boot experience Factors affecting seamless boot Firmware / BIOS Boot Loader Driver initialization OS Startup

Seamless boot experience WDDM 1.2 Firmware initiated native display mode Firmware / driver / OS handoff Fast sleep/ resume times Hardware initialization HCK provides Boot validation / Driver – OS handoff testing Action: Eliminate unnecessary delays and flashes

Metro style apps launch instantly Factors affecting app launch Graphics “device size” Graphics device creation Shader generation Just in case “optimizations”

Metro style apps launch instantly WDDM 1.2 UMD logging for debugging HCK provides measurements for Time to first frame Time to paint contents of an app Memory usage Action: Optimize for Metro style apps

Metro style apps are fast and fluid Factors affecting app performance Efficient memory usage Fast system memory to video memory transfers Fast rendering Efficient rasterization Hardware advances

Metro style apps are fast and fluid WDDM 1.2 features Smooth rotation Offer/Reclaim to reduce memory usage in drivers and apps GPU pre-emption Support for tile based rendering architectures HCK provides measurements for Total memory cost for graphics scenarios # of frames missed and # of concurrent frames missed Action: Release resources back to the system early

Stability and reliability

Stability and reliability Metro style apps, Windows 8 shell, and IE are all using DirectX technologies (D3D11) This means more demands on GPU Longer time between reboots

Stability and reliability WDDM 1.2 delivers better stability and reliability Per engine TDR Improvements to TDR handling UMD logging for debugging GPU pre-emption HCK provides “crash” test suite Action: thoroughly analyze failures and fix them

Developer experiences

Developer experiences Metro style apps depend on DirectX technologies (D3D11) Windows platform promises: Consistency / predictability Reliability Hardware acceleration Develop on app on one system but deploy on everywhere Usage pattern differs for app categories

Developer experiences WDDM is the only Windows 8 driver model WDDM 1.2 delivers confidence DirectX APIs always work API level support for Stereo even on Mono systems Consistent API platform HCK provides extensive conformance suite Action: run tests in all system configurations

Partner experiences

What do kit changes mean for graphics? New UI New “concepts” and “structure” Product types / features / requirements Introduction of “Feature Based Testing” New Automation object model [659] The Windows Hardware Certification Kit

Graphics requirements Windows 8 requirements: Better written, easier to read, more complete Explicit focus on scenarios and justification Missing / ambiguous requirements – clarified Testing at the correct level WDDM 1.2 uses new HCK concepts “graphics products” Full / Render / Display only / etc. Feature based testing

Graphics testing Introduction of graphics performance tests More system level testing Advanced topics Parallel execution of graphics tests Automation APIs Device Families

Graphics testing Do: Thoroughly analyze all failures and fix them Run tests in all configurations Leverage parallel execution All Graphics devices / display adapters pass – repeatedly

Summary

Summary WDDM 1.2 is the Windows 8 driver model HCK provides tools for you to design for Windows 8 Polish Windows 8 scenarios Do more than what certification requires Analyze all failures – analyze the results Surpass performance metrics Test more configurations Invest in hardware features Optimize for Metro style apps

Related sessions [HW-260T] Windows Certification: improvements to the logo program [HW-659T] Certifying hardware with the Windows Hardware Certification Kit [HW-218T] Understanding the Windows 8 graphics driver model [SAC-217T] Graphics on the server [HW-220C] Chalk Talk: Transitioning from XDDM to WDDM [PLAT-752T] Tuning GPU usage for any form factor [PLAT-766T] Introduction to DirectX for Metro style apps [PLAT-751T] 3D Graphics in Metro Style Apps and Games

Further reading and documentation WDDM 1.2 Whitepaper Direct3D 11.1 Features DXGI 1.2 Improvements Unlocking the GPU with Direct3D (PDC 2008) Direct3D on Downlevel Hardware (MSDN) Hardware Support for Direct3D 10Level9 Formats (MSDN) Contact info – dxbuildqa@microsoft.com

thank you Feedback and questions http://forums.dev.windows.com Session feedback http://bldw.in/SessionFeedback

11/27/2018 2:35 AM © 2011 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. © 2011 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.