Tech Support > Microsoft Windows > Drivers > Re: NdisMQueryInformationComplete must be called at IRQL=DISPATCH_LEVEL??? Really?
Re: NdisMQueryInformationComplete must be called at IRQL=DISPATCH_LEVEL??? Really?
Posted by Pavel A. on July 6th, 2003


How can we be sure that NdisAcquireReadWriteLock _always_ raises irql
to dispatch? DDK 3790 documentation doesn't say so.

- Pavel


Stephan Wolf <stewo68@hotmail.com> wrote in message news:<3f05a8f5.4670175@news.t-online.de>...

Posted by Eliyas Yakub [MSFT] on July 8th, 2003


Going thru the code, it seems to me that NdisAcquireReadWriteLock always
raises the IRQL (either by acquiring a spinlock in the Write case or
explicitly raising the IRQL to DISPATCH_LEVEL in the read case).

I will file a bug to get this information added to the doc.


Not really. The doc says that callers typically run at DISPATCH_LEVEL but I
don't think that it must be called at DISPATCH_LEVEL. The code acquires an
internal lock as soon as you enter and it doesn't really make a check to see
whether you are running at DISPATCH_LEVEL. I will check with NDIS team and
see what they have to say.

--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx



Posted by Stephan Wolf on July 9th, 2003


[Note: We've had that already, see
http://groups.google.com/groups?hl=e...crosoft.co m]

Stephan
---
On Tue, 8 Jul 2003 13:39:53 -0700, "Eliyas Yakub [MSFT]"
<eliyasy@online.microsoft.com> wrote:


Similar Posts