Re: WDF-newbie: Sharing memory between application and driver?
- From: "Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 22:18:01 -0800
in addition to all of the other suggestions given you to, you must do
thelocking in your EvtIoInCallerContext callback which is guaranteed to be
in the right context. YOur EvtIoDeviceIoControl routine can be called in
any arbitrary context
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Joerg Hoppe" <jhoppe@xxxxxxxxxxxxxxxx> wrote in message
news:OxiLxjuOHHA.4604@xxxxxxxxxxxxxxxxxxxxxxx
I'm porting an old driver from Compuware Driver::Works to WDF.
I need to share memory between application and my driver.
Problem 1:
My application manages larges buffers. The driver should read/write
data to the application buffer directly. No FileRead/FileWrite ... data
access is not sequentiell.
So I pass a buffer pointer to the driver via an IoCtl.
How do I lock/map this buffer so the driver can access it savely?
Problem 2:
My driver allocates kernel memory with ExAllocatePoolWithTag.
The Application issues an IoCtl and wants to receive a pointer to the
memory.
How do I map the result of WdfMemoryGetBuffer to user process space?
Any Wdf-Examples would be helpful.
Thanks
.
- References:
- WDF-newbie: Sharing memory between application and driver?
- From: Joerg Hoppe
- WDF-newbie: Sharing memory between application and driver?
- Prev by Date: Re: How to simulate a HID device plug-out and plug-in by code and API(or DDK)?
- Next by Date: Re: Modified sample source code distribution from Windows Driver Kits?
- Previous by thread: Re: WDF-newbie: Sharing memory between application and driver?
- Next by thread: Behaviour of driver installations
- Index(es):
Relevant Pages
|
|