From owner-freebsd-alpha Thu Dec 14 11:21:55 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:21:53 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 50F1F37B400; Thu, 14 Dec 2000 11:21:52 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA09252; Thu, 14 Dec 2000 14:21:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eBEJLp141299; Thu, 14 Dec 2000 14:21:51 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 14 Dec 2000 14:21:50 -0500 (EST) To: mjacob@feral.com Cc: John Baldwin , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: References: <14905.6815.2347.450995@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14905.7357.440285.591097@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > > John Baldwin writes: > > > > > > Sounds like lost interrupts. Possibly the interrupt isn't being enabled > > > properly after the ithread finishes running the handler. > > > > Maybe it is time to accept defeat on squelching interrupts at their source > > and leave the IPL raised until the handler is run? > > They may be orthogonal issues. Maybe, but maybe not. Your 4100's missing interrupts sound similar to the missing isa interrupt problems on my UP1000. As Doug mentioned before, leaving the ipl raised would probably be more efficient that groveling around in the interrupt hardware. And it would be nice to not make every platform have to be 100% perfect wrt to enabling/disabling interrupts... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message