The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
being fully aware of security issues for this method I need to develop a driver which allows an application to directly access one bar of PCI device memory.
The reason for this odd technique is beyond the scope of my question.
From within a kernel mode driver I can do this using a sequence like:
MmMapLockedPagesSpecifyCache (specifying non-cached for the physical device)
However, since the driver does not use DMA I thought of creating an UMDF driver.
Mapping of IO space within the driver can be simply done using
and since the driver runs in user space it returns a user space pointer which I assume is only valid in the context of the driver process i.e. the UMDF driver host process.
My question is if there is an analog method to MmMapLockedPagesSpecifyCache to make this pointer valid in the process which calls the driver?
Are named sections available in UMDF? ZwCreateSection etc.?
Thanks in advance for any hint
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Internals & Software Drivers||25 Jan 2021||LIVE ONLINE|
|Developing Minifilters||8 March 2021||LIVE ONLINE|