From owner-freebsd-hackers Sat Apr 19 05:13:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA14314 for hackers-outgoing; Sat, 19 Apr 1997 05:13:17 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14309 for ; Sat, 19 Apr 1997 05:13:15 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id HAA08758; Sat, 19 Apr 1997 07:12:56 -0500 (EST) From: "John S. Dyson" Message-Id: <199704191212.HAA08758@dyson.iquest.net> Subject: Re: special memory device In-Reply-To: <19970419102301.FO34910@uriah.heep.sax.de> from J Wunsch at "Apr 19, 97 10:23:01 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 19 Apr 1997 07:12:56 -0500 (EST) Cc: freebsd-hackers@freebsd.org, krygier@kph.uni-mainz.de, toor@dyson.iquest.net X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Klaus Werner Krygier wrote: > > > This means that the notification about the page fault > > seems to be done by calling the driver's mmap routine. Here I can > > reprogram the interface card. The validation of the now visible window > > is done automatically. The only problem that remains is, how to invalidate > > the pages for the old window so that a page fault will be generated > > again if this window is accessed later. > > Ask John. :) I think you gotta call some *unmap() function, but i'm > not confident with the API, and John never got around to actually > write something like a man page for the VM system (hint, hint :). > I have the question in my queue. Hope to answer it by the end of the weekend. I think that I'll have to craft a subroutine, but it won't be very complicated. I understand about the lack of documentation, the code has stabilized significantly. There'll be some nice stuff coming along again, but I think that the days of vast changes are over. That makes me much less resistant to documentation. The only problem now is time limitations :-(. More good news about the VM code is that we appear to have more competent VM people now. It is suprising to see the really correct fixes coming through!!! :-). John