From owner-freebsd-current  Fri Oct  1  4:27:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id DA89814C12
	for <current@FreeBSD.ORG>; Fri,  1 Oct 1999 04:27:06 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id HAA05080;
	Fri, 1 Oct 1999 07:25:47 -0400 (EDT)
Date: Fri, 1 Oct 1999 07:25:47 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199910011125.HAA05080@pcnet1.pcnet.com>
To: alc@cs.rice.edu, bde@zeta.org.au, current@FreeBSD.ORG,
	jdp@polstra.com, marcel@scc.nl, nate@mt.sri.com, peter@netplex.com.au
Subject: Re: sigset_t: a summary
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marcel Moolenaar wrote:
> So, to start with issue 2:
> 
> To start with the beginning:
> 
> 1. Should the ucontext_t changes be backed out, or is this the
>    way we would like to go? (but only it better :-)

I think we want to keep the ucontext changes.  SUSv2 requires them
when SA_SIGINFO is set.  They'll also make it easier to support
efficient user thread context switches (with get/set/make/swapcontext),
and also provides a hook for a kernel upcall mechanism (scheduler
activations).

Dan Eischen
eischen@vigrid.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message