This brings me to the topic of our latest adventure in Driver Development Land: Code Analysis (CA) in the latest release of the WDK and Visual Studio.ĥ52 Warnings? In a SHIPPING driver? No way! Not an older version, and not a newer version. And that’s why, if you’re one of our clients, we ask you to (please) only build your driver project using the version of the WDK and Visual Studio that we used to build your driver (pretty please). That’s why the policy here at OSR is never upgrade your version of the WDK or VS while you’re in the middle of a project. Once you upgrade, you don’t have the option to roll-back, or choose to use an older version of, say, Code Analysis. That means a new compiler, a new linker, a new Code Analysis engine, and a new version of Static Driver Verifier. When you upgrade to a new version of the WDK and VS, you always get a brand new toolchain. Something to keep in mind is that you can install versions of the WDK “Side by Side” (SxS), so you can always drop back to an older release of the headersĪnd libraries if you have a problem or you specifically want to restrict your driver to using the older headers.īut remember: The only things that are actually SxS are the headers and libs. In general, no… but I suppose it always depends on who you ask. If you’re not up on this, check out the article we wrote on the Spectre and Meldown vulnerabilities back in January. There’s also a nice new section on Driver Security Guidance written by star WDK writer Don Marshall, and that the team here at OSR spent some time on.Īnother reasonably important thing to note is that, without you having to do anything, drivers are now built with the /Qspectre option. I admit to not knowing about either of these features before reading the “What’s New” section for the WDK. There are some interesting new features around PCIe devices that idle in D3Cold being able to specify that they want/need/use auxiliary power. We found interesting the addition of driver and device specific directories (on disk, not in the Registry) for storing state (see IoGetDriverDirectory and IoGetDeviceDirectory). You should read what Microsoft has to say regarding what’s new in driver development because that’s always interesting and worth a few minutes of your time. Note that at the time of this writing () the latest version of Visual Studio is 15.7.1 - and this is definitely the version you should be using. And each new Windows Driver Kit brings with it new functions and features. These days, each new upgrade for Windows brings with it a new Windows Driver Kit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |