Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!ig!agate!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Need info on exceptions
Message-ID: <8808272257.AA03218@cory.Berkeley.EDU>
Date: 27 Aug 88 22:57:50 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 20

:generated interrupts you run into this problem.  Software interrupts,
:however, are generated by the operating system.  Thus, it seems that
:it would be impossible to destroy kernel data from inside a software
:interrupt - they should all be valid.  Software interrupts are
:actually recommended in the RKM for use when you want to do a lot of
:processing inside an interrupt so that the system doesn't slow down -
:this implies that the system multi-tasks during software interrupts
:and so the software interrupt should appear as a task to the O/S.
:
:Any Gurus want to comment on this?

	Yes I would.  You are dead wrong.  Sorry.

	SOFTWARE INTERRUPTS ARE JUST LIKE HARDWARE INTERRUPTS!  The only
difference is that normal hardware interrupts can occur while one is processing
a software interrupt.  The system does not multi-task while one is processing
a software interrupt.  Neither can you AllocMem() inside a software interrupt.
same rules apply as for hardware interrupts.

				-Matt