From owner-freebsd-current Tue Apr 18 17:29:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA28520 for current-outgoing; Tue, 18 Apr 1995 17:29:13 -0700 Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA28514 for ; Tue, 18 Apr 1995 17:29:10 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.9/8.6.5) with UUCP id RAA18630; Tue, 18 Apr 1995 17:28:35 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.8/8.6.6) id QAA11703; Tue, 18 Apr 1995 16:35:06 -0700 From: Frank Mayhar Message-Id: <199504182335.QAA11703@exit.com> Subject: Re: Memory fill patterns To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Tue, 18 Apr 1995 16:35:05 -0700 (PDT) Cc: rgrimes@gndrsh.aac.dev.com, current@FreeBSD.org In-Reply-To: <9504181908.AA00747@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 18, 95 03:08:34 pm X-Mailer: ELM [version 2.4 PL23beta2] Content-Type: text Content-Length: 550 Sender: current-owner@FreeBSD.org Precedence: bulk > Unfortunately, Rod missed the point, or rather, he saw one of them and > missed the rest. Here is the rationale for the choice of 0xdeadbeef > (or 0xdeadbee1): > > 4) When used as an address, it's unlikely to be mapped. Well, 4) is actually not true, at least for the version of 80x86-based SVR4.2 I hack at work. 0xdeadbeef, or anything in the range 0xd0000000 - 0xdfffffff is very, very often a valid kernel address. I don't know how this maps to FreeBSD (not very well, I suspect), but it's a consideration. -- Frank Mayhar frank@exit.com