From owner-freebsd-threads@FreeBSD.ORG Wed May 7 14:51:07 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55B4D37B401; Wed, 7 May 2003 14:51:07 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12C9643F3F; Wed, 7 May 2003 14:51:04 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by attbi.com (sccrmhc03) with ESMTP id <2003050721510200300bfj1fe>; Wed, 7 May 2003 21:51:03 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA48337; Wed, 7 May 2003 14:51:00 -0700 (PDT) Date: Wed, 7 May 2003 14:50:59 -0700 (PDT) From: Julian Elischer To: John Baldwin In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Daniel Eischen cc: David Xu Subject: Re: kern_threads.c.. lock question.. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2003 21:51:07 -0000 On Wed, 7 May 2003, John Baldwin wrote: > > On 07-May-2003 Julian Elischer wrote: > > > > > > On Tue, 6 May 2003, David Xu wrote: > I thought singlethreading only suspended other threads and that > they can be resumed later if need be. I suppose in that case > you wouldn't use P_SINGLE_EXIT though. exactly. "single thread yourself by means of murdering all the competition" > > > Please let's optimize later and get things working _first_. > Right now current has this really annoying piss-ant of a bug > where I lose my keyboard every so often in X, probably due to > a locking bug I haven't managed to track down yet (feels an > awful lot like a lost wakeup). Its not anything urgent.. it just came up in conversation with david.. I'm not in a hurry to change it. certainly not before 5.1. (It only affects KSE processes anyhow) What we were actually discussing was a potential corruption of the KSE sigmask in userland. This was just something we noticed while passing through..