From owner-freebsd-arch@FreeBSD.ORG Thu Nov 4 23:22:08 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80F1F16A4CE for ; Thu, 4 Nov 2004 23:22:08 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 194AF43D54 for ; Thu, 4 Nov 2004 23:22:08 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iA4NO5hX028452; Thu, 4 Nov 2004 16:24:05 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <418AB9E2.6070708@freebsd.org> Date: Thu, 04 Nov 2004 16:23:14 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Willem Jan Withagen References: <418AB176.9030604@withagen.nl> <418AB649.80809@freebsd.org> <418AB888.7070305@withagen.nl> In-Reply-To: <418AB888.7070305@withagen.nl> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "arch@freebsd.org" Subject: Re: Booting questions .... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 23:22:08 -0000 Willem Jan Withagen wrote: > Scott Long wrote: > >> The loader has a protected mode environment. It is apparently not all >> that hard to port memtest86 into it. I'd highly recommend doing this >> rather than trying to hack up the early pmap initialization. > > > Is that so.... I was unable to find that. :( can you give me a pointer?? Sorry, I know of some private efforts, but not any public efforts. > > And like I wrote in the previous discussion. The algorithms are not all > that difficult to write. It is getting easy access to the memory. > If you look at memtest86, you'll that they have to get a lot of work > done to get to the actual job: memory testing. > And that only for the x86 type processors, which are already served by > memtest86. > > But reading your question, the answer would be: > too complex to get this figured out Not too complex, just full of landmines. I'm not sure that you can put generic code into the VM system to do this without concerning yourself about the per-arch pmap layout. Also, how do you handle traps that are generated by the memtest? That's another per-arch thing that you have to think about. Scott