From owner-freebsd-hackers Sat Nov 8 02:50:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00489 for hackers-outgoing; Sat, 8 Nov 1997 02:50:09 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from d198-232.uoregon.edu (d198-232.uoregon.edu [128.223.198.232]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00484 for ; Sat, 8 Nov 1997 02:50:05 -0800 (PST) (envelope-from mini@d198-232.uoregon.edu) Received: (from mini@localhost) by d198-232.uoregon.edu (8.8.5/8.8.5) id CAA21051; Sat, 8 Nov 1997 02:49:59 -0800 (PST) Message-ID: <19971108024958.28488@micron.mini.net> Date: Sat, 8 Nov 1997 02:49:58 -0800 From: Jonathan Mini To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: x86 gods; advice? Suggestions? References: <19971108023810.31291@micron.mini.net> <199711081043.VAA00922@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <199711081043.VAA00922@word.smith.net.au>; from Mike Smith on Sat, Nov 08, 1997 at 09:13:34PM +1030 X-files: The Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith stands accused of saying: > > I was hoping to avoid that solution. This is an implementation for a library. > > It all falls down to one this : the vm86 arena has to be in the 0-1M memory > > range. If I'm implementing a library for this, I can't really do that. Hence > > I have to create a new context that I can destroy in order to set up the > > vm86 arena. > > Two possible solutions; use a coprocess running the vm86 thread as a > sort of "graphics processor" (involves a context switch between > operations, but you could stack them), or wait for the vm86 sysarch() > stuff that comes with the vm86 stuff I am working on. (Kernel entry > and two context switches per call.) That is how I originally planned writing the code. I am working on a method that uses vfork(2) to see if it is any faster/slower/doesn't-make-a-difference. Not much is really done in the vm86 task, just calls to do things like set the video mode and such. > Initially you can only run a single interrupt and have no way of > providing any other data, but we can probably come up with something > much more efficient (eg. mmap of a section of the vm86 address space). > > Once the initial code is in place, I'll be taking suggestions. 8) > > mike > > -- Jonathan Mini Ingenious Productions Software Development P.O. Box 5693, Eugene, Or. 97405 "A child of five could understand this! Quick -- Fetch me a child of five."