使用Windows Driver Foundation开发驱动程序

windows

需积分: 1 126 浏览量更新于2024-06-18 收藏 8.25MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"《使用Windows驱动程序框架开发驱动程序》是由Penny Orwick和Guy Smith合著，由Microsoft Press在2007年出版的928页的技术书籍。本书详细介绍了如何使用Windows驱动程序框架（WDF）来开发稳定、可靠的Windows驱动程序。" 在Windows操作系统中，驱动程序是操作系统与硬件设备之间的桥梁，它们负责处理硬件的特殊功能并使得操作系统能够与硬件进行通信。Windows驱动程序框架（Windows Driver Framework，简称WDF）是微软推出的一种驱动开发模型，它提供了一种结构化和模块化的开发方式，旨在简化驱动程序的开发过程，提高驱动程序的稳定性和可靠性。 Part1 - Getting Started with WDF：这部分介绍了WDF的基础知识，包括WDF的引入、Windows驱动程序的基本概念以及WDF的基本原理。读者将了解WDF如何帮助开发者构建符合现代Windows系统需求的驱动程序，并熟悉WDF的核心概念。 Chapter 1 - Introduction to WDF：这一章详细解释了WDF是什么，为何选择WDF进行驱动开发，以及WDF相较于其他驱动开发方法的优势。它涵盖了WDF的主要特点，如对象模型、事件回调和框架管理的设备生命周期。 Chapter 2 - Windows Driver Fundamentals：本章深入讲解了Windows驱动程序的基础，包括驱动程序的作用、类型、以及如何在Windows环境中运行和管理驱动程序。它还可能涵盖设备驱动程序接口（DDI）和驱动程序的安装与配置。 Chapter 3 - WDFFundamentals：在这里，作者会介绍WDF的基本组件和工作流程，包括驱动程序的创建、对象的管理和框架如何处理设备的插拔和电源管理。 Part2 - Exploring the Frameworks：这部分详细探讨了WDF的框架结构，包括框架的总体概述、对象模型以及驱动程序的初始化和结构。 Chapter 4 - Overview of the Driver Frameworks：这一章将阐述WDF的不同组件，如KMDF（Kernel-Mode Driver Framework）和UMDF（User-Mode Driver Framework），它们的区别以及适用于哪些类型的驱动程序。 Chapter 5 - WDF Object Model：介绍WDF的对象模型，这是理解WDF工作方式的关键。它涵盖了对象的创建、引用计数、事件回调以及对象间的依赖关系。 Chapter 6 - Driver Structure and Initialization：本章将详细讨论如何设置驱动程序的结构，如何初始化和配置框架，以及如何正确地启动驱动程序。 Part3 - Applying WDFFundamentals：这部分将实际应用WDF的基本概念，涉及插拔和电源管理、I/O处理、同步机制、诊断和调试。 Chapter 7 - Plug and Play and Power Management：介绍如何处理设备的即插即用（PnP）和电源管理事件，这是驱动程序必须支持的重要功能。 Chapter 8 - I/O Flow and Dispatching：这一章深入到驱动程序的I/O处理，包括请求的创建、调度和完成，以及中断服务例程（ISR）和DPC（ Deferred Procedure Call）的概念。 Chapter 9 - I/O Targets：讨论I/O目标，这是WDF中用于与硬件或其他驱动程序通信的关键概念。 Chapter 10 - Synchronization：讲述了驱动程序内部的同步机制，确保对共享资源的安全访问，避免数据竞争和死锁。 Chapter 11 - Driver Tracing and Diagnosability：介绍如何利用WDF的跟踪和诊断工具来调试驱动程序，提高问题定位的效率。 Chapter 12 - WDF Support Objects：这部分涵盖了WDF提供的辅助对象和服务，以增强驱动程序的功能和性能。 Chapter 13 - UMDF Driver Template：针对用户模式驱动程序框架，介绍了如何使用UMDF模板创建驱动程序，以及UMDF在特定场景下的优势。 Part4 - Additional Topics for KMDF Drivers：这部分针对KMDF驱动程序，讨论了框架之外的话题，如调度、线程管理和其他高级主题。 Chapter 14 - Beyond the Frameworks：本章探讨了在框架提供的基础之上，如何扩展和优化KMDF驱动程序，可能涉及到自定义调度策略、非默认的I/O队列处理等。 Chapter 15 - Scheduling, Threads, and Other Advanced Topics：详细讨论了线程管理、调度策略和其他高级技术，帮助开发者提升驱动程序的性能和响应性。《使用Windows驱动程序框架开发驱动程序》是一本全面的指南，涵盖了从驱动开发入门到高级技术的各个方面，为开发者提供了构建高效、可靠的Windows驱动程序的必要知识和实践指导。

资源详情

资源推荐

Getting Started with Driver Development

To follow the examples in this book and to use the WDF frameworks, you must install the current Windows

Driver Kit (WDK). The WDK contains most of the resources you need to develop drivers, such as tools,

documentation, and libraries. The following sections provide some guidelines and tips for installing software

and finding the samples and tools discussed in this book.

Importa

nt?

Always use the most recent version of the

WDK. This book assumes that you are using

WDK Build 6000 or a later version. If you are

already developing Windows drivers, you need

to install Build 6000 or a later version to obtain

the components discussed in this book. Static

Driver Verifier for KMDF drivers and PREfast

driver-specific annotations require the WDK

version provided with the Beta 3 release of

Microsoft Windows Server Code Name

"Longhorn," or a later version.

System Requirements for Driver Development

You can develop and build KMDF drivers for Windows 2000 or later versions of Windows. You can build

UMDF drivers for Windows XP or a later version of Windows. You can use any recent version of Windows to

build your drivers. To target a driver for a particular version and CPU architecture, you specify the appropriate

build environment configuration when you use the Build utility.

However, you should plan to install, test, and debug your driver on a system that is running the target version

of Windows, with hardware that is the same as or similar to the hardware on your customers' systems.

Importa

nt?

Always use the most recent version of the

Debugging Tools for Windows, as described

later in this chapter.

To debug KMDF drivers, you need two computers: one to host the debugger and the other to host the driver

you want to debug. Kernel-mode driver bugs commonly cause system crashes and can corrupt the file

system, causing loss of data-so it's necessary to have the debugger and driver on separate computers.

To debug UMDF drivers, you can run the debugger and driver on the same computer or run the two on

separate systems. You can also use a single computer with different versions of Windows on separate

partitions for many of these tasks. However, a common practice is to have a development computer plus at

least one additional computer dedicated to testing and debugging.

We recommend the following hardware for a developer's work configuration:



A computer with a multicore processor or multiple processors. At a minimum, your processor

should support hyperthreading. If you test your drivers only on a uniprocessor system, you might

not detect certain types of bugs, such as race conditions. In addition, the Windows Logo Program

requires that all submitted drivers pass compatibility tests for multiprocessor systems.



A 64-bit computer that runs x64 versions of Windows. Certain types of critical errors can be

detected only on 64-bit systems. The Windows Logo Program requires that your driver support both

32-and 64-bit systems.

Tip

If you develop and test WDM drivers by using WDK Build 6000 or later, you can

use the same build environments to develop drivers with WDF.

How to Obtain and Install the WDK

The WDK, which contains the Driver Development Kit (DDK), is the driver developer's primary resource. The

WDK contains the bulk of what you need to develop drivers, as described in the following sections.

The WDK supports driver development for the Microsoft Windows NT family of operating systems, starting

with Windows 2000. The WDK is released periodically, and the version is typically associated with a

particular Windows release. However, that's just a convenient way of indicating the release date. In fact, each

Page 16

WDK release supports building drivers for all hardware platforms and all versions of Windows that Microsoft

supports under the life cycle support policy. In 2007, the WDK supports building drivers for Windows 2000,

Windows XP, Windows Server 2003, Windows Vista, and Windows Server "Longhorn."

You should always use the latest version of the WDK. This practice guarantees that you have current

documentation and tools, including all updates and fixes made since the previous release.

To Obtain the WDK

See the WHDC Web site at http://www.microsoft.com/whdc/ for information about obtaining the

current WDK.

New versions are released in conjunction with associated product releases, such as Windows beta

and RTM releases and major developer events such as WinHEC. The WHDC Web site also provides

information about which versions of Windows are supported by the current WDK.

If you download the ISO for the WDK, burn a CD or DVD to create the installation media.

To Install the WDK

Insert the WDK installation media to run the installation application.

Read the WDK Release Notes to check for any installation issues.

Install required prerequisites.

The installation application checks your system and enables buttons under WDK Prerequisite Setup

Packages for any features that are not present. You might not need all of these features, but you

probably want the .NET Framework, Version 2.0, and Microsoft Document Explorer to view the

documentation.

Under WDK Setup Package Features, click Install

Inside

Out?

By default, the WDK installs on your C drive in

a root folder named WinDDK \BuildNumber. If

you install multiple WDK versions, the WDK

installation wizard places each WDK version

under its own build number.

Tip?

Because you can choose to install the WDK

on other drives the %wdk% environment

variable is used in this book to refer to the

WDK root folder.

WDK Libraries

The WDK includes static libraries (LIBs), dynamic-link libraries (DLLs), and the WDF libraries that you need

for developing WDF drivers:



Redistributable co-installer DLLs The WDK contains redistributable co-installers for UMDF and

KMDF. The co-installers are used during driver installation to install the associated framework

runtime support on a user's computer, if the runtime is not already present. Drivers dynamically bind

with the frameworks that the co-installers install. To make the co-installers easier to identify, their

names include the WDF version number. There are separate versions of the co-installers for each

supported CPU architecture.

Chapter 20, "How to Install WDF Drivers," describes the co-installers.



Debugger extensions The WDF debugger extensions are specialized, WDF-specific commands

that run in the context of the WinDbg debugger. The debugger extensions are packaged in two

DLLs: WudfExt.dll contains the UMDF extensions, and WdfKd.dll contains the KMDF extensions.

Separate versions of the debugger extensions are provided for each supported CPU architecture.

Chapter 22, "How to Debug WDF Drivers," describes WinDbg and the extensions.



Libraries The WDK contains a number of static libraries. KMDF drivers bind statically with

WdfDriverEntry.lib and WdfLdr.lib. You can choose to implement UMDF drivers by using the Active

Template Library (ATL), a C++ template library that is designed to simplify the process of

implementing COM objects.

Inside

Out?

KMDF libraries are located under

%wdk%\lib\wdf\kmdf. ATL libraries are located

Page 17

under %wdk%\lib\atl.

WDK Documentation

This book is only an introduction to WDF development. For all of the necessary information to develop a fully

functional device driver, see the WDK documentation. That documentation provides detailed reference pages

for every function exposed in the WDF device driver interface (DDI). The WDK documentation also contains

conceptual material, design and implementation guidelines, and documentation for the WDK tools.

To Run the WDK Documentation from the Start Menu



On the taskbar, click Start, and then click:

All Programs > Windows Driver Kits > BuildNumber > Help > WDK Documentation

Tip

You can view the WDK documentation online as part of the MSDN Library-online at

http://msdn.microsoft.com. Locate the Microsoft Win32 and COM Development node in the MSDN

Library table of contents, and then find Windows Driver Kit. The online version of the WDK

documentation is updated quarterly.

WDK Tools

The WDK contains a substantial set of tools for development and testing. Most are command-line tools that

run in a command window, but some are conventional Windows applications with graphical user interfaces.

Some tools for testing include the following:



Tracing Chapter 11, "Driver Tracing and Diagnosability," describes how to use WPP tracing and

the associated WDK tools to trace execution and assist in debugging.



Driver Verifier and other runtime tools Chapter 21, "Tools for Testing WDF Drivers," discusses

the runtime verification tools for testing drivers.



Static verifiers Chapter 23, "PREfast for Drivers," and Chapter 24, "Static Driver Verifier," provide

details about using static verifier tools.

Note-Info

To run some of the tools in Windows Vista, you must specify that you want the tool to run with

elevated privileges, even if you already have administrative privileges. See "User Account Control" on MSDN

for details-online at http://go.microsoft.com/fwlink/?LinkId=80621

To Run an Application on Windows Vista with Elevated Privileges

On the taskbar, click Start, right-click the application, and then click Run as administrator

If you already have administrative privileges, Windows Vista displays a User Account Control dialog

box asking for permission to proceed.

To run the application, click Continue

If you do not have administrative privileges, Windows Vista asks for administrative credentials.

To Open a Command Window with Elevated Privileges

On the taskbar, click Start, right-click Command Window, and then click Run as

administrator

Click Continue and provide credentials, if prompted.

Any application that you run from that command window, including any Windows-based application,

also has elevated privileges.

WDK Samples

The WDK includes an extensive set of samples that show common types of drivers you might develop. These

samples contain well-designed working code and are extensively commented.

Inside

Out?

The WDF samples are installed with the WDK in %wdk%\src\kmdf and

%wdk%\src\umdf. Each sample is installed in its own folder with the same name as

the driver.

Tip

Before you

Page 18

successfully.

The Skeleton sample driver is simple so that you can use it to learn the basics of how a UMDF driver

works. It's also a good starting point for implementing a functional driver, because most UMDF drivers

can use most of the code in the Skeleton sample driver with little or no modification. You can add code

incrementally to handle the requirements of your particular device.

Inside

Out?

The Skeleton sample driver is installed with the WDK in the %wdk%\src\umdf

\skeleton folder.



Fx2_Driver This sample is a USB driver that was specifically designed for learning purposes.

The Fx2_Driver works with the OSR USB FX2 Learning Kit device from Open System Resources (OSR),

as described later in this chapter. Fx2_Driver is simple because the device itself is not very complicated.

However, the driver works with a real device and demonstrates a range of basic UMDF features, including

how to handle read, write, and device I/O control requests.

Code from the Fx2_Driver sample driver appears throughout this book in examples to show how UMDF

drivers work. Other samples are also included-in this book and in the WDK-to illustrate features that

Fx2_Driver does not support.

Inside

Out?

Fx2_Driver is located under the %wdk%\src\umdf\usb\fx2_driver folder. Each

subfolder contains a variant of the driver. The driver in the Step1 folder is a minimal

implementation. The Step2 through Step5 folders contain increasingly full-featured

versions of the driver. The Final folder contains the complete driver and is the sample

that is used in this book. The \Exe subfolder contains source code for a simple

console application that can be used to operate the device and exercise the

capabilities of the driver.

About KMDF Samples

The WDK provides many KMDF samples. If you are a new WDF developer, we recommend that you examine

the Toaster and Osrusbfx2 samples, which are used throughout this book. You can examine other samples

for more information about other features that these samples do not use, such as DMA or interrupt handling:



Toaster This software driver simulates the behavior of real devices in Windows.

The Toaster driver is not quite as basic as the Skeleton driver, but nevertheless serves as a useful

starting point for understanding KMDF drivers. The Toaster sample is made up of a collection of related

drivers, including bus, filter, and function drivers.

Inside

Out?

The Toaster sample is located in the %wdk%\src\kmdf\toaster folder. Several

subfolders contain different related drivers. The best place to start is with the function

driver located under %wdk%\src\kmdf\toaster\func.

Two drivers in that subfolder contain a different version of the driver: a basic one named Simple, and a

full-featured version named Featured. The %wdk%\src\kmdf\toaster\exe folder contains the source code

for several test applications that you can use to exercise the driver's capabilities.



Osrusbfx2 This sample is a USB driver built for kernel mode.

Code from the Osrusbfx2 sample driver appears throughout this book in examples to show how KMDF

drivers work. This sample does not demonstrate all of the features of KMDF. The %wdk%\src\kmdf folder

in the WDK contains other samples that illustrate features that Osrusbfx2 does not support.

This sample is the kernel-mode equivalent of Fx2_Driver. It has almost the same capabilities as

Fx2_Driver, and the structure and code are quite similar.

Inside

Out?

Osrusbfx2 is located in %wdk%\src\kmdf\osrusbfx2, which includes six subfolders.

The Step1 through Step5 and the Final folders contain successively more

sophisticated versions of the driver. Each version has similar capabilities to the

corresponding Fx2_Driver version. The \Exe subfolder contains the source code for a

simple test application.

Tip

Use the Osrusbfx2

Page 20

剩余866页未读，继续阅读

nNightKil

粉丝: 0
资源: 6

使用Windows Driver Foundation开发驱动程序

Developing.Drivers.with.the.Windows.Driver.Foundation

Developing Drivers with the Microsoft Windows Driver Foundation

Microsoft Press - Developing Drivers with the Windows Driver Foundation (Apr 2007).chm

developing drivers with the windows driver foundation chm

WINDOW 驱动开发教程

windows驱动开发入门

developing drivers with windows pdf

stm32f407sdk

developing apps with gpt-4 and chatgpt

The Great Learning.txt

developing apps with gpt-4 and chatgpt pdf

What is the significance of developing renewable energy in the light of different kinds of pollution mentioned in Reading 3?

stm32f10x_stdperiph_lib_v3.5.0

What is the first English letter for developing your company

the importance of developing a heathy lifestyle among college students.

The+Firmware+Package+(STM32Cube+FW_G4+V1.5.2)+or+one+of+its+dependencies+required+by+the+Project+is

.net core runtimes

Write a speech which can be read in 5 minutes, and the topic is"the power of self confidence"

write a thesis about scientific activity survey in middle school

What are the c++ engineers developing

最新资源