I wonder if my understant about interrupt is right.
According to the description about interrupt in Wikipedia, IRQ is refer to Maskable interrupt. So I think most of the hardware interrupt is Maskable interrupt(include mouse and keyboard).
In my view, interrupt service routine (ISR), also known as interrupt handler, is the routine described in IDT(interrupt describe table).
So after excuting the CLI directive, the mouse and keyboard won’t work.
Thank you for your reply.
Well first executing CLI in your driver falls under the category of
really bad things to do. Second, Wikipedia is referring to the general
hardware concept and drivers use an abstracted version of this that the
OS provides. So no your ISR is not stored in the IDT, the OS stores its
routine in the IDT, and calls your ISR as appropriate.
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“daedae11” wrote in message news:xxxxx@ntdev:
> I wonder if my understant about interrupt is right.
> According to the description about interrupt in Wikipedia, IRQ is refer to Maskable interrupt. So I think most of the hardware interrupt is Maskable interrupt(include mouse and keyboard).
> In my view, interrupt service routine (ISR), also known as interrupt handler, is the routine described in IDT(interrupt describe table).
> So after excuting the CLI directive, the mouse and keyboard won’t work.
> Thank you for your reply.
And the reason why you are at the assembly level? If you’re writing your driver in assembly ? ok ? I will not go down the “Stupid idea” scenarios we have run many times.
You executed a CLI and wonder why, or you executed CLI and want to know if what you got was expected? Yup ? it certainly was expected. Most likely you’ll find LOTS of other interrupting devices not working as well. If this is an exercise to learn, then I would say you have learned. Typically, executing CLI/STI outside of the realm of the control of the OS, as in your own driver, is NOT a good thing for the stability of the system.
Gary Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
On Nov 28, 2011, at 11:06 AM, daedae11 wrote:
I wonder if my understant about interrupt is right.
According to the description about interrupt in Wikipedia, IRQ is refer to Maskable interrupt. So I think most of the hardware interrupt is Maskable interrupt(include mouse and keyboard).
In my view, interrupt service routine (ISR), also known as interrupt handler, is the routine described in IDT(interrupt describe table).
So after excuting the CLI directive, the mouse and keyboard won’t work.
Thank you for your reply.— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer