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
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
