Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

IoConnectInterrupt

0 views
Skip to first unread message

Phil Vincent

unread,
Dec 1, 1997, 3:00:00 AM12/1/97
to

I'm aware of the basic differences between edge and level sensitive
interrupts and the basic architecture of PCI vs. ISA interrupts...but
could someone tell me or maybe guess what NT does differently when
IoConnectInterrupt() is called with a Latched vs. LevelSensitive value
for the InterruptMode parameter on an i386 platform??

I want to run some legacy ISA binaries on a PCI interrupt and I can
force them to set the Shared parameter...but I'm afraid I'm stuck with
the existing InterruptMode parameter...I was hoping it was a "don't
care" on i386 particularly since PCI Interrupt router would take care of
level/edge xlation....but apparently i'm mistaken...

Thanks,
Phil Vincent

Assaf Wodeslavsky

unread,
Dec 2, 1997, 3:00:00 AM12/2/97
to

In my experience NT does not care what
I set your mode to.
It is always LevelSensitive for PCI devices.

assaf.

Phil Vincent <pvin...@systemsoft.com> wrote in article
<348368...@systemsoft.com>...

Paul Sanders

unread,
Dec 2, 1997, 3:00:00 AM12/2/97
to

Read last month's (Vol 3, NO 11) issue of Windows NT Magazine. There is an
article by Mark Russinovich entitled "Inside NT's Interrupt Handling". See
also http://www.ntinternals.com/publ.htm, but the article is not there (just
interesting reading).

Basically, there are only a handful of interrupt entry points (IDT). Two of
these are chained (level sensitive) and unchained (edge triggered). These
kernel-mode chained handler knows that more than one ISR might own the
vector. The unchained handler knows that only one ISR is registered for
this vector.

-Paul

Phil Vincent wrote in message <348368...@systemsoft.com>...

0 new messages