Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!ukc!inmos!braa!davidb
From: davidb@braa.inmos.co.uk (David Boreham)
Newsgroups: comp.os.os9
Subject: Re: Interrupt handling error in most OSK drivers ???
Message-ID: <1879@brwa.inmos.co.uk>
Date: 21 Aug 89 14:58:43 GMT
References: <1772@ethz.UUCP>
Sender: news@inmos.co.uk
Reply-To: davidb@braa.UUCP (David Boreham)
Organization: none
Lines: 14


Yes ! I too have always wondered about this. I am doing a driver
for hardware which almost invariably interrupts *before* the process
sleeps. I would have thought that the F$sleep system call aught to
unmask the interrupt, otherwise, as the previous poster says, the
interrupt will be taken *before* the process is actually sleeping.
Consequently, the signal from the "bottom-half" of the driver will 
be lost forever. I can't believe that this problem is real, but I
can't see what the answer is. (Also, my driver screws-up in a way
consistent with the problem--this proves nothing however:) .

David Boreham, INMOS Limited | mail(uk): davidb@inmos.co.uk or ukc!inmos!davidb
Bristol,  England            |      (us): uunet!inmos-c!davidb
+44 454 616616 ex 543        | Internet : @col.hp.com:davidb@inmos-c