Date: Fri, 1 Oct 1999 07:25:47 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.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 Message-ID: <199910011125.HAA05080@pcnet1.pcnet.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910011125.HAA05080>