From owner-freebsd-threads@FreeBSD.ORG Mon Feb 9 14:09:53 2004 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 3EFDE16A4CE; Mon, 9 Feb 2004 14:09:53 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9BA743D1D; Mon, 9 Feb 2004 14:09:52 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <200402092209510120089hh9e>; Mon, 9 Feb 2004 22:09:52 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA71228; Mon, 9 Feb 2004 14:09:50 -0800 (PST) Date: Mon, 9 Feb 2004 14:09:49 -0800 (PST) From: Julian Elischer To: John Baldwin In-Reply-To: <200402091641.37061.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@FreeBSD.org Subject: Re: TDF_INTERRUPT 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: Mon, 09 Feb 2004 22:09:53 -0000 This is david's code but I would assume that the flag is not cleared until the signal is actually deliverred which would probably occur more towards the user/kernel boundary.. (This is not a definative answer). julian (looking at the code now).