From owner-freebsd-current Tue May 23 5:25:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 5AF1537B977 for ; Tue, 23 May 2000 05:25:13 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12uDjW-000Hp4-00; Tue, 23 May 2000 19:24:26 +0700 Date: Tue, 23 May 2000 19:24:26 +0700 (ALMST) From: Boris Popov To: Bruce Evans Cc: Matthew Dillon , Garrett Wollman , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Anyone else seeing jumpy mice? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 May 2000, Bruce Evans wrote: > The patch seems to have completely broken fast interrupts. > GET_FAST_INTR_LOCK is neither necessary nor sufficient as far as I can see. > The necessary and sufficient locking is done by COM_LOCK() in individual > drivers. The patch changed GET_FAST_INTR_LOCK from s_lock(&fast_intr_lock), > which does nothing very well, to `sti(); get_mplock(); cli();', which > essentially de-prioritizes "fast" interrupts from "higher than the highest" > (higher than clock interrupts which are nominally highest) to "lower than > the lowest" (lower than all normal interrupts, all software interrupts, > and all MP-unsafe syscalls). Yes, this explains problems with sio. > Untested fix: Thank you. It works and no crashes experienced yet. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message