I decided that instead of going the route of writing a generic filter driver framework in WDM, I'd stay on the bleeding edge and try my hand at a KMDF filter.

Writing a KMDF Filter: It's Easy, Really! If you have no clue what a WDFDEVICE_INIT structure is or what the hell an I/O event callback is, then you should check out some of our previous KMDF articles such as A Soft Life - Implementing Software-Only Drivers Using KMDF. So, I decided that there had to be a better way.īefore we start, I'm assuming you already have a vague idea as to how to write a KMDF driver. Even though I'm only using this filter as a one-off, I still want it to be correct. This worked great and all, but after giving it a closer look my confidence in the DiskPerf code started to wane (any code that still does *nextIrpStack = *currentIrpStack doesn't belong anywhere but my recycle bin). To isolate the offending code path, I gutted all of the WMI crap out of DiskPerf (for what felt like the 500 th time) and added a DbgBreakPoint when an IRP that matched my parameters came in. For example, we recently had an issue where reads to certain regions on the disk appeared to be causing us a great deal of pain.

Second of all, you must frequently find yourself needing to write a quick, throwaway filter for some incredibly annoying purpose. If you're like me, first of all - I'm sorry. The NT Insider, Vol 13, Issue 1, Jan-Feb 2006 | Published: 08-Mar-06| Modified: 08-Mar-06Ĭlick Here to Download: Code Associated With This Article Zip Archive, 29 KB KMDF Filter Driver: 30-Minutes - Installation: Ah.Somewhat Longer

Install kmdf driver