From owner-freebsd-alpha Thu Dec 14 11:25: 3 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:25:01 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0458F37B400; Thu, 14 Dec 2000 11:24:56 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA26347; Thu, 14 Dec 2000 11:24:57 -0800 Date: Thu, 14 Dec 2000 11:24:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: John Baldwin , alpha@FreeBSD.ORG Subject: RE: mutex/ithread jitters? In-Reply-To: <14905.7357.440285.591097@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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... No arguments from me on this one (after all, ahem, I suggested it first!). But I haven't gotten around to breaking free the day or so it will take to do this. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message