From owner-freebsd-threads@FreeBSD.ORG Sun Aug 17 20:16:23 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 C282C37B401; Sun, 17 Aug 2003 20:16:23 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EFA243FA3; Sun, 17 Aug 2003 20:16:23 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h7I3GMuN001821; Sun, 17 Aug 2003 23:16:22 -0400 (EDT) Date: Sun, 17 Aug 2003 23:16:22 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Marcel Moolenaar In-Reply-To: <20030817231246.GA17207@dhcp42.pn.xcllnt.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: David Xu Subject: Re: First draft: rewrite of {get|set|swap}context(3) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 03:16:24 -0000 On Sun, 17 Aug 2003, Marcel Moolenaar wrote: > On Mon, Aug 18, 2003 at 06:47:52AM +0800, David Xu wrote: > > > > Then doesn't signal context in signal handler have a UCF_SIGMASK ? > > Yes. > > > void (*__sa_sigaction)(int, struct __siginfo *, ucontext_t *ucp); > > the context *ucp should have UCF_SIGMASK now. > > We never define uc_flags currently. We only copyout() uc_sigmask and > uc_mcontext. Hence, the uc_flags field is garbage. As is the uc_stack > field. > > > I think it should be UCF_NOSIGMASK. But for libkse, we really needn't > > this kind of hack, because M:N thread in kernel always masks all signals, > > you can always SIGFILLSET(&uc.uc_sigmask) before call set_context. > > I tried this, but it didn't fix mutex_d. I don't think the signal mask problem is the cause of mutex_d failing, but I did notice it when trying to kill the test. The mutex_d problem seems to be that either _ia64_restore_context() or _ia64_break_setcontext() are not working. -- Dan Eischen