From owner-freebsd-current  Tue Jun  4 19:47:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA11388
          for current-outgoing; Tue, 4 Jun 1996 19:47:48 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA11360
          for <FreeBSD-current@FreeBSD.org>; Tue, 4 Jun 1996 19:47:44 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id VAA02177; Tue, 4 Jun 1996 21:42:41 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199606050242.VAA02177@dyson.iquest.net>
Subject: Re: Vm fixes NG
To: terry@lambert.org (Terry Lambert)
Date: Tue, 4 Jun 1996 21:42:41 -0500 (EST)
Cc: james@miller.cs.uwm.edu, terry@lambert.org, FreeBSD-current@FreeBSD.org,
        fcurrent@jraynard.demon.co.uk, grog@lemis.de
In-Reply-To: <199606050047.RAA27881@phaeton.artisoft.com> from "Terry Lambert" at Jun 4, 96 05:47:51 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

This discussion of trying to solve the problem of a GUI leaving the
console in a state that the kernel doesn't know how to change during
a system crash is interesting.  There is a potential solution (hack)
that I don't remember being mentioned.  HACK ALERT!!!: Specify a callback
into user space -- wired specially, with a special system call, that the
kernel (syscons, pcvt, etc) can call in the case of a crash to fix the problem.
To make it easiest on the kernel VM people, it would be nice if it would be
a self-contained module and PIC.  We don't support user space ISRs (yet), but
this isn't very different from an user space ISR.

Just a thought.

John