From owner-freebsd-hackers Fri Nov 1 10:49:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA17702 for hackers-outgoing; Fri, 1 Nov 1996 10:49:13 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA17681 for ; Fri, 1 Nov 1996 10:49:06 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA28151; Fri, 1 Nov 1996 11:42:21 -0700 From: Terry Lambert Message-Id: <199611011842.LAA28151@phaeton.artisoft.com> Subject: VM answer requested To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 1 Nov 1996 11:42:21 -0700 (MST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199611011413.AAA05539@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 2, 96 00:43:49 am X-Mailer: ELM [version 2.4 PL24] 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 I've brought this up before, but... FreeBSD has a number of very valuable features in its VM to aid in tracking coding errors... unmapping page 0, etc.. What about the aligned access bit in recent Intel processors? I'd like to be able to turn on the bit so that I get a fault (and it kills the offending process) when an unaligned access occurs. I'd also like to get kernel faults if this happens in the kernel (it is my opinion that it should never be allowed to happen in the kernel, and there should be a sanitization pass to insure it). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.