From owner-freebsd-hackers Fri Sep 8 10: 1: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2FCE737B42C for ; Fri, 8 Sep 2000 10:01:02 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA15859; Fri, 8 Sep 2000 13:00:43 -0400 (EDT) Date: Fri, 8 Sep 2000 13:00:42 -0400 (EDT) From: Daniel Eischen To: "Ralf S. Engelschall" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: makecontext & friends ? In-Reply-To: <20000908161542.A87619@engelschall.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Sep 2000, Ralf S. Engelschall wrote: > > In article <20000908151942.A15852@lamu.hermes.si> you wrote: > > > are there any plans to implement makecontext() & friends > > functions in FreeBSD? > > I don't know of any plans myself, but I would appreciate that we support this > standardized ucontext(3) API in FreeBSD. The API is actually not the problem, > the question is on what should this API internally be based? On an own > mechanism or on an existing mechanism (jmp_buf, etc)? My implementation of it was based on a trapframe, so it would be easy to pass a ucontext_t to the kernel and have it switch to the context at appropriate times (scheduler activations). A trapframe is the same as a sigcontext_t (ucontext_t) for i386 but not for the alpha. I think I got around this by adding a type field to the ucontext (or mcontext) to indicate which format it was for alpha. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message