Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.


Tim_RobertsTim_Roberts Member - All Emails Posts: 13,007
While trying to answer a question, I just noticed something strange in
the documentation for the ISR for message-signaled interrupts at

The system can call an /InterruptMessageService/ routine even when
the routine's interrupt has not occurred. For example, if a
message-signaled interrupt is shared, /InterruptMessageService/ can
be called for interrupts belonging to other devices. The routine
must check whether the value for the /ServiceContext/ parameter
matches the value passed to *IoConnectInterruptEx*. If the value
does match, /InterruptMessageService/ handles the interrupt and
returns *TRUE*. Otherwise, /InterruptMessageService/does not handle
the interrupt and returns *FALSE*.

They cannot mean what they wrote here.  How can I possibly check whether
the value for ServiceContext matches what I passed to
IoConnectInterruptEx?  If I could establish my context independently, I
wouldn't need the ServiceContext parameter at all.  What do you suppose
they were trying to say?

Tim Roberts,
Providenza & Boekelheide, Inc.

Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.


  • Pavel_APavel_A Member Posts: 2,674
    Very strange indeed. MSIs can be shared now? On which kind of platform?

    -- pa
  • anton_bassovanton_bassov Member Posts: 5,013
    > How can I possibly check whether the value for ServiceContext matches what
    > I passed to IoConnectInterruptEx??

    Actually, I am more "impressed" my MSI sharing part......

    Concerning the above question, you can always save a pointer that you have passed to IoConnectInterruptEx() in some global variable (or array in case of multiple calls to IoConnectInterruptEx() for different instances of your device) so that you can identify your targets. No matter how stupid and awkward the above mentioned approach is, it is going to sort out the issue you are asking about. However, the idiocy of MSI sharing suggestion is so profound that it just leaves me sort of speechless....

    Anton Bassov
  • Alex_GrigAlex_Grig Member Posts: 3,238
    I think that's a copy-paste error
  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 7,284
    It's GOT to be a doc bug.


    Peter Viscarola

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA