From owner-freebsd-arch Sat Jun 10 6:55:51 2000 Delivered-To: freebsd-arch@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8135B37B81D for ; Sat, 10 Jun 2000 06:55:48 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 20104 invoked from network); 10 Jun 2000 13:55:45 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 10 Jun 2000 13:55:45 -0000 Date: Sat, 10 Jun 2000 23:55:41 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Daniel Eischen Cc: Doug Rabson , arch@FreeBSD.ORG Subject: Re: Syscalls and execve In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Jun 2000, Daniel Eischen wrote: > On Sat, 10 Jun 2000, Doug Rabson wrote: > > The trapframe which is created for syscall is identical to the trapframe > > for exceptions and interrupts, its just not fully populated with register > > values. > > On a related subject, the alpha sigcontext is different than the > trapframe. This makes implementing {get,set}context slightly more > difficult because they have to know which frame is in the machine > context. For the new threads architecture (similar to scheduler It's different on i386's too. It is certain to be different if the floating point state is separate and too expensive to save in the trap frame. The i386 also has complications for vm86 mode. > activations), the context of threads that become unblocked in > the kernel is passed out to the user threads library. I want to > add {get,set}context as library routines and use them to handle > both signal contexts and trapframes as passed out of the kernel. I don't see how they can be implemented as pure library routines, since they will have to get and set kernel state. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message