From owner-freebsd-hackers Wed Jun 4 01:26:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA05958 for hackers-outgoing; Wed, 4 Jun 1997 01:26:51 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (root@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA05952 for ; Wed, 4 Jun 1997 01:26:47 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.5) id RAA27842; Wed, 4 Jun 1997 17:42:52 +1000 Received: from localhost.devetir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id RAA16094; Wed, 4 Jun 1997 17:45:32 +1000 (EST) Message-Id: <199706040745.RAA16094@ogre.dtir.qld.gov.au> To: Pat Bozeman cc: freebsd-hackers@freebsd.org Subject: Re: Virtual address question for VM guru's References: In-Reply-To: from Pat Bozeman at "Wed, 04 Jun 1997 04:36:38 +0000" Date: Wed, 04 Jun 1997 17:45:31 +1000 From: Stephen McKay Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, 4th June 1997, Pat Bozeman wrote: >What I would like to do is map specific process address ranges into the >kernel's virtual address space and then keep track of the new kernel >virtual address which should point to the correct physical address >regardless of which process is active. Have a look at /sys/kern/sys_pipe.c for some hints. I think you should be able to do what you want using the same techniques. Buyer beware, of course! I've never done this myself. Stephen.