From owner-freebsd-hackers Mon Mar 8 18: 1:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 1F95514FCE for ; Mon, 8 Mar 1999 18:01:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02140; Mon, 8 Mar 1999 17:55:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903090155.RAA02140@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Li ChunAn (Nokia/Beijing)" Cc: "'freebsd-hackers@FreeBSD.ORG'" Subject: Re: interrupt mechanism In-reply-to: Your message of "Tue, 02 Mar 1999 07:16:05 +0200." <199903022342.BAA24824@ns10.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 17:55:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello > I am a kernel programmer. Would you like to tell me something detailed about > the interrupt mechanism and kernel programming guides? Where can I find the > IRQ-handler table in kernel codes? FreeBSD generates the interrupt handler table dynamically at runtime, as interrupts can be moved from one handler to another, or chained between multiple handlers. You can read the low-level interrupt handler code for the i386 in /usr/src/sys/i386/isa/icu_* (for uniprocessor kernels) and /usr/src/sys/i386/isa/apic_* (for SMP kernels). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message