From owner-freebsd-current Wed Jul 3 2:48: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C973437B400 for ; Wed, 3 Jul 2002 02:48:00 -0700 (PDT) Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6110043E64 for ; Wed, 3 Jul 2002 02:48:00 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 32134 invoked from network); 3 Jul 2002 09:47:58 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 3 Jul 2002 09:47:58 -0000 Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g639liM25533; Wed, 3 Jul 2002 05:47:44 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 03 Jul 2002 05:47:52 -0400 (EDT) From: John Baldwin To: Julian Elischer Subject: Re: KSE signal problems still Cc: Andrew Gallatin , freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 03-Jul-2002 Julian Elischer wrote: > > Expanding on my own mail: > > On Wed, 3 Jul 2002, Julian Elischer wrote: > >> On Wed, 3 Jul 2002, John Baldwin wrote: >> >> > >> > Well then it must be full of races then that were fixed since DP1. >> > *sigh* I wonder how many other things were lost and need to be >> > reimplemented. >> > > > Almost anything you checked into psignal will need looking at. > It may not be mising but since signals for threaded processes are > fundamentally different than signals for non threaded processes, some > things "just don't apply". > > for example if you checked in something to code that just doesn;t exist > any more in a KSE kernel, what is the correct integration? > > Each one has to be evaluated on it's own.. The one in question here was fairly simple, it just expanded the sched_lock locking some. The argument could be made that you shouldn't be checking in stuff until you know how it works, etc., or that you could commit in smaller pieces (say, get multiple threads per process for kernel processes working in the scheduler and just ignoring userland-only things like signals until you have the other working). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message