From owner-freebsd-arch Fri Mar 16 1:31: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 187C137B718; Fri, 16 Mar 2001 01:31:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 14dqZb-000EvY-0V; Fri, 16 Mar 2001 09:31:03 +0000 Received: from salmon.nlsystems.com (salmon [10.0.0.3]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f2G9Tl475070; Fri, 16 Mar 2001 09:29:47 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 16 Mar 2001 09:29:47 +0000 (GMT) From: Doug Rabson To: John Baldwin Cc: Matthew Jacob , , Matt Dillon Subject: Re: Proposal for the CPU interrupt API In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Mar 2001, John Baldwin wrote: > > On 16-Mar-01 Matthew Jacob wrote: > > > > > >> > >> :I would hope it would actually disable interrupts. > >> > >> On all cpu's or just the current cpu? > > > > Undefined. This depends on the architecture. Some architectures don't have a > > global interrupt lockout mechanism. Some architectures vary as to whether or > > not interrupts can be directed to one CPU, broadcast to all, or only for a > > specific CPU. > > > > I think it's safe to say that given your specific platform's interrupt > > mechanism, this disable_intr disables for this CPU only, or for all. > > Yep. I think that on the Alpha the IPL may be shared among all CPU's or may be > per-CPU but I'm not sure. On the x86 it would only be for the local CPU, but > all that any calling code should depend on is that it disables interrupts for > the current CPU. On the alpha, IPL is a cpu-local attribute as far as I know. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message