Re[2]: disable interrupts

How is a level-triggered interrupt acknowlegded with an IRET ?
AFAIK the cpu blocks at that irql (and lower ones).

| Norbert Kawulski | mailto:xxxxx@stollmann.de |
| Stollmann T.P.GmbH, Development | http://www.stollmann.de |
–If it’s ISDN or Bluetooth, make sure it’s driven by Stollmann–

“You are never alone with a schizophrenic.”

“Moreira, Alberto” wrote in message
> news:xxxxx@ntdev…
>> It’s easier than it looks. Just copy the whole IDT into your own memory,
>> frig it, and change the IDTR. Hey, maybe we should add a “mockIDT” class
> to
>> our DriverWorks! It’s only 256 entries anyway, what’s the big deal ?
>>

> If your note was intended as flame bait, I’ll swallow.

> That is simply THE most hideous, irresponsible, architecturally abberant,
> hack I have ever heard in my 20+ years of driver writing.

> You really have no idea of what side-effects this may cause in the O/S,
> Alberto. Or what problems doing this might cause for other drivers. Not to
> mention, if I frig the IDT in MY driver, and you frig it in YOURS, then
> what’s the result?? Duh!? This isn’t DOS. It isn’t Windows 3.1 – It’s a
> real, general purpose, operating system.

> Because I’m in a particularly good mood, I might grant that such techniques
> might be applicable in a very specific environment (embedded tool, etc).

> To suggest, however, that this is a reasonable, generically applicable,
> solution to a common question such as the one posted is not engineering. And
> it certainly does no service to the community of developers who are trying
> to learn to write Windows drivers. One does not use a sledge hammer when a
> screwdriver can accomplish what’s required.

> I s’pose if all you HAVE is a sledge hammer, then everything looks like a
> pile of rock though…

> Peter
> OSR

> —
> You are currently subscribed to ntdev as: xxxxx@stollmann.de
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Peter…

I’m not in the troll business. But you’re talking to someone who programs at
hardware level, who’s in the business of running independent and sometimes
in spite of the OS. If doing this kind of thing was hideous, irresponsible,
architecturally aberrant, neither SoftIce nor BoundsChecker would work,
would they ? Or VMWare, for that matter ? There’s more to kernel level
programming than writing drivers that adhere to the party line !

If I don’t want to be interrupted, I don’t want to be interrupted - and I’m
not going to let the OS tell me whether or not I’m entitled not to be
interrupted. If I decide not to be interrupted, you can be sure the OS is
not going to interrupt me, and I’ll get the OS out of the way if need be.

To me, the OS is just a component - it is NOT the guy in charge, nor is it a
cop.

Alberto.

-----Original Message-----
From: Peter Viscarola [mailto:xxxxx@osr.com]
Sent: Thursday, September 20, 2001 12:18 PM
To: NT Developers Interest List
Subject: [ntdev] Re: disable interrupts

“Moreira, Alberto” wrote in message
news:xxxxx@ntdev…
> It’s easier than it looks. Just copy the whole IDT into your own memory,
> frig it, and change the IDTR. Hey, maybe we should add a “mockIDT” class
to
> our DriverWorks! It’s only 256 entries anyway, what’s the big deal ?
>

If your note was intended as flame bait, I’ll swallow.

That is simply THE most hideous, irresponsible, architecturally abberant,
hack I have ever heard in my 20+ years of driver writing.

You really have no idea of what side-effects this may cause in the O/S,
Alberto. Or what problems doing this might cause for other drivers. Not to
mention, if I frig the IDT in MY driver, and you frig it in YOURS, then
what’s the result?? Duh!? This isn’t DOS. It isn’t Windows 3.1 – It’s a
real, general purpose, operating system.

Because I’m in a particularly good mood, I might grant that such techniques
might be applicable in a very specific environment (embedded tool, etc).

To suggest, however, that this is a reasonable, generically applicable,
solution to a common question such as the one posted is not engineering. And
it certainly does no service to the community of developers who are trying
to learn to write Windows drivers. One does not use a sledge hammer when a
screwdriver can accomplish what’s required.

I s’pose if all you HAVE is a sledge hammer, then everything looks like a
pile of rock though…

Peter
OSR


You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com