From owner-cvs-all@FreeBSD.ORG Wed Jul 14 14:43:40 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC98016A4CE; Wed, 14 Jul 2004 14:43:40 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57E5043D49; Wed, 14 Jul 2004 14:43:40 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6EEhN6n053202; Wed, 14 Jul 2004 10:43:23 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6EEhNWW053198; Wed, 14 Jul 2004 10:43:23 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 14 Jul 2004 10:43:23 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Alfred Perlstein In-Reply-To: <200407140702.i6E724mV093920@repoman.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_event.c src/sys/sys eventvar.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2004 14:43:40 -0000 On Wed, 14 Jul 2004, Alfred Perlstein wrote: > Log: > Make FIOASYNC, FIOSETOWN and FIOGETOWN work on kqueues. Have you tried testing this on a kqueue used to monitor signals? I'd draw your particular attention to the following newly enabled code path: pgsigio() -> psignal() -> tdsignal() -> do_tdsignal() -> KNOTE() -> knote() -> KNOTE_ACTIVATE() -> knote_enqueue() -> kqueue_wakeup() -> pgsigio() It strikes me that adding sigio support to kqueue opens a massive can of worms, not least of which is how you prevent the above from causing the system to panic, not to mention how you handle locking in what is otherwise a set of leaf functions in kqueue. I'd like it if you could back this out until locking for kqueue is resolved, as while this is no doubt a useful feature, having the locking working is much more useful to us for 5.3. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research