IoConnectInterrupt - STATUS_INVALID_PARAMETER
in [Device Drivers]
|
From: Tim Roberts on 16 Jun 2010 01:41 Mohit Gupta <MohitGupta(a)discussions.microsoft.com> wrote: > >Then how do I hook software interrupts? What you are saying seems as if >IoConnectInterrupt can only be used for handling interrupts for PnP supported >hardware devices. That's correct. Windows does not support software interrupts. Just that simple. There are supported methods for communicating between user-mode and kernel-mode. Use them. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: Mohit Gupta on 16 Jun 2010 03:44 "Tim Roberts" wrote: > > That's correct. Windows does not support software interrupts. Just that > simple. There are supported methods for communicating between user-mode > and kernel-mode. Use them. It's clearly documented that IDT consists of some OS specific interrupt handlers, others for hardware interrupts (in total 15) and rest for software interrupts. "Windows does not support software interrupts." - Did you mean software interrupt IDT entries are hooked to some dummy interrupts handlers which are not used by windows at all? > -- > Tim Roberts, timr(a)probo.com > Providenza & Boekelheide, Inc. > . >
From: Scott Noone on 16 Jun 2010 09:48 > It's clearly documented that IDT consists of some OS specific interrupt > handlers, others for hardware interrupts (in total 15) and rest for > software > interrupts. You're misunderstanding something. Even if you weren't, just because the architecture supports something doesn't mean that Windows exposes it as a general mechanism. -scott -- Scott Noone Consulting Associate OSR Open Systems Resources, Inc. http://www.osronline.com "Mohit Gupta" <MohitGupta(a)discussions.microsoft.com> wrote in message news:FF92A4C2-AF44-40CE-BBCF-510C16775E13(a)microsoft.com... > "Tim Roberts" wrote: > >> >> That's correct. Windows does not support software interrupts. Just that >> simple. There are supported methods for communicating between user-mode >> and kernel-mode. Use them. > > It's clearly documented that IDT consists of some OS specific interrupt > handlers, others for hardware interrupts (in total 15) and rest for > software > interrupts. > > "Windows does not support software interrupts." - Did you mean software > interrupt IDT entries are hooked to some dummy interrupts handlers which > are > not used by windows at all? > > >> -- >> Tim Roberts, timr(a)probo.com >> Providenza & Boekelheide, Inc. >> . >>
From: Tim Roberts on 18 Jun 2010 01:06
Mohit Gupta <MohitGupta(a)discussions.microsoft.com> wrote: > >It's clearly documented that IDT consists of some OS specific interrupt >handlers, others for hardware interrupts (in total 15) and rest for software >interrupts. Sure. The processor supports software interrupts. The Windows kernel does not. Today's processors support many features that cannot be used by user-mode programs. >"Windows does not support software interrupts." - Did you mean software >interrupt IDT entries are hooked to some dummy interrupts handlers which are >not used by windows at all? What I mean is that executing a software interrupt instruction in a user-mode process on Windows will result in a fault that terminates the process. The plumbing is simply not present. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc. |