From owner-freebsd-hackers Sat Dec 26 20:25:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07235 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 20:25:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07230 for ; Sat, 26 Dec 1998 20:25:13 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id XAA13377 for ; Sat, 26 Dec 1998 23:24:55 -0500 (EST) Date: Sat, 26 Dec 1998 23:24:54 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: Questions about interrupt handling Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I know that FreeBSD handles interrupts on a software basis which means that we do not mask any interrupt off in 8259. I am just wondering if a certain interrupt is masked off in 8259 or it does not get serviced quick enough, what will the device controller (such as disk controller) respond? Will it re-issue the interrupt or just give up? Or will it NOT generate another interrupt until the previous one has been serviced? Maybe different device controllers behave differently. Thanks for any help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message