Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
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/
Fw: Re: About time spend when processing Dispatch routine-?
OSR_Community_User
Member Posts: 110,217
in NTDEV
From: "Prekupec Boris" <[email protected]>
Sent: Tuesday, May 30, 2000 4:04 PM
> Matt and all others,
> I meant DPC routine(s) first as my driver doesn't require an interrupt
from
> device to process an I/O operation. It can catch interrupts event but I
> wasn't able to test that.
I see.
> So I have designed driver to work also through
> IOCTL codes with DeviceIoControl (don't recall the exact name) function
> call inside win32 application. As I presume that device doesn't rise
> interrupt I use DPCs as some kind of WatchDog timer.
I'm not quite sure I understand the situation you're describing but, yes,
direct calls from an application into your driver will occur at
PASSIVE_LEVEL.
> As other routines I also meant I/O routines (StarIo, AdapterControl etc.)
> But I think I have received all answers I needed,
> thanks to you all for your contribution,
Glad to help.
Just be careful in the future how you use the term "dispatch routine". To
most driver writers, this means an IRP_MJ_* handler which, as I described,
typically has nothing to do with execution at DISPATCH_LEVEL.
- Matt
Sent: Tuesday, May 30, 2000 4:04 PM
> Matt and all others,
> I meant DPC routine(s) first as my driver doesn't require an interrupt
from
> device to process an I/O operation. It can catch interrupts event but I
> wasn't able to test that.
I see.
> So I have designed driver to work also through
> IOCTL codes with DeviceIoControl (don't recall the exact name) function
> call inside win32 application. As I presume that device doesn't rise
> interrupt I use DPCs as some kind of WatchDog timer.
I'm not quite sure I understand the situation you're describing but, yes,
direct calls from an application into your driver will occur at
PASSIVE_LEVEL.
> As other routines I also meant I/O routines (StarIo, AdapterControl etc.)
> But I think I have received all answers I needed,
> thanks to you all for your contribution,
Glad to help.
Just be careful in the future how you use the term "dispatch routine". To
most driver writers, this means an IRP_MJ_* handler which, as I described,
typically has nothing to do with execution at DISPATCH_LEVEL.
- Matt
Howdy, Stranger!
| 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! | ||
| Kernel Debugging | 13-17 May 2024 | Live, Online |
| Developing Minifilters | 1-5 Apr 2024 | Live, Online |
| Internals & Software Drivers | 11-15 Mar 2024 | Live, Online |
| Writing WDF Drivers | 26 Feb - 1 Mar 2024 | Live, Online |