I can't imagine why you would think it has anything to do with KEVENTS.
Take a look at the various mutexs. Also, you are incorrect on
KeWaitForSingleObject it does not put the thread into a wait state unless
the object is not available.
--
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website:
http://www.windrvr.com
Blog:
http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
"Murugesan" <> wrote in message
news:41EC25C5-EC76-4620-ACA5-...
> Hi all,
> From the WDF documentation, WdfWaitLock is the replacement for
> KEVENT(WDM).
> So if a thread calls wdfwaitlockacquire() will it be put in wait state
> eventhough the lock object is available.
> In other words, is wdfwaitlockacquire() & wdfwaitlockrelease() an exact
> replacement of Kewaitforsingleobject() & KeSetEvent() ?
>
> Thanks,
> Murugesan
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4593 (20091110) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4593 (20091110) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com