From owner-freebsd-current Tue Apr 2 06:20:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA26480 for current-outgoing; Tue, 2 Apr 1996 06:20:08 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA26471 for ; Tue, 2 Apr 1996 06:20:04 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0u46wE-0003vrC; Tue, 2 Apr 96 06:20 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id OAA03491; Tue, 2 Apr 1996 14:20:03 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Bruce Evans cc: freebsd-current@freefall.freebsd.org, kuku@gilberto.physik.rwth-aachen.de Subject: Re: calcru: negative time: In-reply-to: Your message of "Tue, 02 Apr 1996 23:17:57 +1000." <199604021317.XAA23396@godzilla.zeta.org.au> Date: Tue, 02 Apr 1996 14:20:02 +0000 Message-ID: <3489.828454802@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Alternatively, could we make a check in spl*() so that if splhigh has been > >active >long< time we will print a warning ? > > I plan to do this too. This should only be enabled for debugging. My > current tests have been detecting lots of problems but haven't been any > help for finding where the high latency comes from. The problem should > be reported by stopping at a breakpoint in spl0 or in doreti before the > cpl has been reduced. Then there will be a chance of seeing what set > cpl high for too long. Couldn't you just record the %eip in splhigh() ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.