|
Writing Windows WDM Device DriversAs the figure illustrates, the test drivers only write to the DebugPrint driver, while the Monitor only reads. This section will not look at all the DebugPrint driver code. The Plug and Play and Initialization code is largely the same as earlier WDM drivers. You should install just one DebugPrint device in the Other Devices category. The interesting code is in the dispatch routines in Dispatch.cpp, along with a main header file DebugPrint.h. These files and the other source files can be found on the book's software disk. Design The DebugPrint driver uses a similar technique of storing all written trace events in a doubly-linked list called EventList. When the DebugPrint Monitor program starts, it reads all the available events. It then leaves one read request outstanding. When a new trace event is written by a test driver, the Monitor read request is satisfied straightaway. This design ensures that trace events get to the Monitor application as soon as possible. This means that the DebugPrint driver has to be able to queue up incoming read requests ...» |
Код для вставки книги в блог HTML
phpBB
текст
|
|