From owner-freebsd-current  Mon Aug 18 11:34:21 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA08527
          for current-outgoing; Mon, 18 Aug 1997 11:34:21 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA08521;
          Mon, 18 Aug 1997 11:34:13 -0700 (PDT)
Received: (from root@localhost)
	by dyson.iquest.net (8.8.6/8.8.5) id NAA14815;
	Mon, 18 Aug 1997 13:34:02 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199708181834.NAA14815@dyson.iquest.net>
Subject: Re: big kernels, part II
In-Reply-To: <221.871917592@critter.dk.tfs.com> from Poul-Henning Kamp at "Aug 18, 97 05:19:52 pm"
To: phk@dk.tfs.com (Poul-Henning Kamp)
Date: Mon, 18 Aug 1997 13:34:02 -0500 (EST)
Cc: dyson@freebsd.org, current@freebsd.org
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-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I've found the problem with big kernels.  The problem is that the
> "PSE" code assumes that a kernel text+data+bss+symbols+misc data will
> always fit in one 4MB "super-page".
> 
> This is obviously not always the case.
> 
> To reproduce just compile a kernel with COPTFLAGS set to "-a -g" and you 
> will see it (if your cpu supports PSE that is).
> 
> Any chance you can fix this John ?
> 
Hmmm....  I never meant to map the entire kernel, but just the first 4MB.
I'll look at it.

John