From owner-freebsd-hackers Sat Nov 8 02:47:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00316 for hackers-outgoing; Sat, 8 Nov 1997 02:47:47 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (ppp13.portal.net.au [202.12.71.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00282 for ; Sat, 8 Nov 1997 02:47:40 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id VAA00922; Sat, 8 Nov 1997 21:13:36 +1030 (CST) Message-Id: <199711081043.VAA00922@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jonathan Mini cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: x86 gods; advice? Suggestions? In-reply-to: Your message of "Sat, 08 Nov 1997 02:38:10 -0800." <19971108023810.31291@micron.mini.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Nov 1997 21:13:34 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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.) 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