1 / 23

Getting a Logo for Your Windows Driver Framework Driver

Getting a Logo for Your Windows Driver Framework Driver. Neslihan Bulut Software Design Engineer in Test Windows Driver Foundation nebulut@microsoft.com. Agenda. Why get drivers logo’ed ? WDF Logo Requirements WDF Logo Testing. Why Get Drivers Logo’ed ?.

pebbles
Télécharger la présentation

Getting a Logo for Your Windows Driver Framework Driver

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Getting a Logo for YourWindows Driver Framework Driver NeslihanBulut Software Design Engineer in Test Windows Driver Foundation nebulut@microsoft.com

  2. Agenda • Why get drivers logo’ed? • WDF Logo Requirements • WDF Logo Testing

  3. Why Get Drivers Logo’ed? • Windows Logo Program identifies drivers that are designed and tested to deliver compatible experiences with Windows • Windows Logo provides Winqual signature • Trusted by every machine • Logo ensures: • Driver package integrity • Driver installs without any warnings or requests from an administrator • On 64-bit Windows unsigned drivers won’t load

  4. WDF Logo Requirements

  5. WDF Logo Tests • UMDF-specific & KMDF-specific Driver Settings • DDI Fault Injection and Driver Reliability Tests • WDF Redistributable Version Checks • INF File Validation with CheckInf

  6. UMDF Settings • Object Tracking will be enabled • Application Verifier will be on for the Host Process • Use !wudfext.Wudfdumpobjects in the debugger to see any leaked objects • Object Tracking will help catch WDF object leaks • UMDF will cause a driver stop because of leaked objects • If you discover object leaks, set Reference Count Tracking On • This setting provides add-release history of references

  7. KMDF Settings • Driver Verifier will be enabled • WDF Verifier will be enabled • Enhanced Verifier will be enabled • New feature for WDF 1.9 • Performs IRQL and Critical Region checks for event callbacks • Handle Tracking will be enabled via TrackHandles registry value for all WDF objects • Set TrackHandles registry value to * in the Wdfsubkey of driver’s Parameters key, WdfVerifier tool can be used for this. • With WDF 1.9, running the driver under Driver Verifier also enables WDF Verifier by default • Setting VerifierOn registry value to 0 in the Wdfsubkey of the driver’s Parameters key turns this off

  8. DDI Fault Injection • WDFTester from WDK Tools is used for fault injection • DDI return values will be fault-injected • When DDI return values are fault-injected, DDI out parameters can be fuzzed upon exit by the logo test • Drivers must inspect DDI return values properly

  9. WDFTester • Available in %wdk%\WDKVersionNumber\tools\wdf\wdftester\ • Uses advanced kernel techniques similar to Driver Verifier for fault injecting the DDIs called from your driver • Fault injection is currently limited to DDIs that return NTSTATUS codes • Has a WMI Interface for use by applications and scripts • WdfTesterScript.wsf is provided in WDK as a reference • This script provides command line interfaces to call into Wdftesterwmi methods • For more information, see wdftester.html in WDK • Provides call logging through traces • Use Traceview.exe (provided with the WDK) to view the call log

  10. WDFTester (continued) • 1. Register Driver 2. Execute Test • 3. GetDdiCallInfo 4. ConfigureDdiFi • 5. Execute Test 6. Unregister Driver • WdfTester order of execution

  11. WDFTester (continued) • 1. Register Driver 2. Inject own test • 3. GetDdiCallInfo • 4. ConfigureDdiFi 5. Inject own test • 6. Unregister Driver • Use with your own tests • At the 2nd and 5th stages run a test against the driver • With any test, Wdftester can collect DDI’s called from the driver and it can be used to fault inject those DDIs

  12. WDFTester Scenario • Cscript wdftesterscript.wsf runtest <DriverName> <DeviceId> • Execute Test phase uses Device Disable Enable Test from WDK • Example with Osrusbfx2 from WDF samples

  13. WDFTester Scenario (continued)

  14. WDFTester Scenario (continued)

  15. WDFTester Scenario (continued)

  16. Logo Test • Logo Test runs in 2 phases • 1st phase determines the DDIs called • 2nd phase configures fault injection on those DDIs • If the driver calls a DDI n times, fault injection can: • Occur at random calls, or • Be configured for any call of the DDI, inclusive 1 … n • 3 tests from WDK are run against the driver: • Device Disable/Enable • Sleep Test • PnP Tests

  17. Logo Test (continued) • Fault injection exercises these DDIs: • WdfDriverCreate • WdfDeviceCreate • WdfWaitLockCreate • WdfIoQueueCreate • WdfDeviceCreateDeviceInterface • WdfDeviceAssignMofResourceName • WdfWmiInstanceCreate • WdfDeviceOpenRegistryKey • WdfRegistryQueryULong • WdfWaitLockCreate • WdfDeviceCreateDeviceInterface

  18. Logo Test (continued) • … and these DDIs: • WdfDeviceAssignMofResourceName • WdfWmiInstanceCreate • WdfDeviceConfigureRequestDispatching • WdfUsbTargetDeviceCreate • WdfUsbTargetDeviceSelectConfig • WdfUsbTargetDeviceRetrieveInformation • WdfDeviceAssignS0IdleSettings • WdfDeviceAssignSxWakeSettings • WdfUsbTargetPipeConfigContinuousReader • WdfIoTargetStart • . . .

  19. WDF Redistributable Version Checks • Drivers can be packaged for logo with only latest RTM fre versions of the WDF co-installers • Before Windows 7 RTM, WDF v1.9 drivers can be submitted for logo only if: • Driver is not packaged with pre- RTM v1.9 co-installers • Before WDF v1.9 RTM, v1.9 drivers can be submitted for logo provided that there is not any co-installer in the driver package • KMDF drivers Inf file must adhere to the following requirements • Doesn’t have WDF co-installer section • Doesn’t reference WDF co-installer (WdfCoinstaller<Version>.dll) anywhere • UMDF drivers Inf file must adhere to the following requirements • Has WDF Co-installer section. WDF Co-installer section; • Has AddReg directive, it associates only the config co-installer (WUDFCoinstaller.dll) with the device • Doesn’t have CopyFiles directive • Doesn’t reference update co-installer (WUDFUpdate_<version>.dll) anywhere • Logo is required for Windows 7 only

  20. INF File Validation • Validation checks for: • Properly structured WDF-specific sections of INF • Coinstaller section • WDF section • KMDF Install section in KMDF drivers • UMDF Install section in UMDF drivers • Refer to MSDN and Developing Drivers with the Windows Driver Foundation book for details about WDF sections • CatalogFiledirective in the [Version] section of INF • Service Names, Hardware Ids , CLSIDs and Display names against the ones provided with WDK samples • Don’t copy/paste service names, Hardware Ids, CLSIDs and Display Names from WDF samples

  21. Call to Action • Test using WdfTester • Test WDF drivers with WDF Verifier and DriverVerifier • Test UMDF drivers with Application Verifier • Diagnose with WDF-specific registry settings enabled, by using WdfVerifier application • http://msdn.microsoft.com/en-us/library/cc264238.aspx • Use the latest RTM fre co-installers • Review and provide feedback on logo program requirements via https://winqual.microsoft.com • Certify your driver’s quality with Windows Logo

  22. Resources • Book: Developing Drivers with the Windows Driver Foundation • http://www.microsoft.com/MSPress/books/10512.aspx • Windows Logo Program • http://www.microsoft.com/whdc/winlogo/default.mspx • http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx • WDF Testing and INF Documentation on MSDN • WdfTester: WDF Driver Testing Toolset http://msdn.microsoft.com/en-us/library/cc264231.aspx • Specifying WDF Directiveshttp://go.microsoft.com/fwlink/?LinkID=82953 • Installing the Framework's Co-installerhttp://msdn.microsoft.com/en-us/library/aa490024.aspx

More Related