Date: Wed, 7 May 2003 14:50:59 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: John Baldwin <jhb@FreeBSD.org> Cc: David Xu <davidxu@freebsd.org> Subject: Re: kern_threads.c.. lock question.. Message-ID: <Pine.BSF.4.21.0305071438340.47162-100000@InterJet.elischer.org> In-Reply-To: <XFMail.20030507170152.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0305071438340.47162-100000>