From owner-freebsd-arch  Thu Mar 15 18:36:53 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 346AB37B71A; Thu, 15 Mar 2001 18:36:51 -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 SAA20530;
	Thu, 15 Mar 2001 18:36:49 -0800
Date: Thu, 15 Mar 2001 18:36:45 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Matt Dillon <dillon@earth.backplane.com>
Cc: John Baldwin <jhb@FreeBSD.ORG>, arch@FreeBSD.ORG
Subject: Re: Proposal for the CPU interrupt API
In-Reply-To: <200103160232.f2G2WgZ54833@earth.backplane.com>
Message-ID: <Pine.BSF.4.21.0103151836370.75234-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


I would hope it would actually disable interrupts.


On Thu, 15 Mar 2001, Matt Dillon wrote:

>     Is this API going to disable interrupts physically or simply flag
>     that interrupts are disabled in the per-cpu state, aka the way the
>     old splhigh() mechanism used to?
> 
> 							-Matt
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-arch" in the body of the message
> 


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