From owner-freebsd-arch  Fri Mar 16  7:28:36 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1CECF37B719; Fri, 16 Mar 2001 07:28:34 -0800 (PST)
	(envelope-from mjacob@feral.com)
Received: from beppo (beppo [192.67.166.79])
	by feral.com (8.9.3/8.9.3) with ESMTP id HAA22686;
	Fri, 16 Mar 2001 07:28:37 -0800
Date: Fri, 16 Mar 2001 07:28:33 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Benno Rice <benno@FreeBSD.ORG>
Cc: Doug Rabson <dfr@nlsystems.com>, John Baldwin <jhb@FreeBSD.ORG>,
	arch@FreeBSD.ORG
Subject: Re: Proposal for the CPU interrupt API
In-Reply-To: <20010316220848.A30533@rafe.jeamland.net>
Message-ID: <Pine.BSF.4.21.0103160726160.53255-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > 
> > (in the PPC architecture I believe that page faults are interrupts)
> 
> Not quite.  Page faults and external interrupts are both classed as
> 'exceptions'.  External interrupts however can be turned on or off using the
> EE bit of the machine state register without disabling page fault (DSI or ISI)
> exceptions.

Ah! Thanks for the clarification.

What I had gotten my notion from was from AIX- if you have a spinlock
contested and take a page fault in the kernel, you lock up. 

-matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message