From owner-freebsd-hackers Thu Jul 1 15:40:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2829614DE8 for ; Thu, 1 Jul 1999 15:40:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B9D8679; Fri, 2 Jul 1999 06:40:28 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: Andrew Gallatin , hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? In-reply-to: Your message of "Thu, 01 Jul 1999 15:14:39 MST." <199907012214.PAA01520@dingo.cdrom.com> Date: Fri, 02 Jul 1999 06:40:28 +0800 From: Peter Wemm Message-Id: <19990701224028.B9D8679@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Personally, I think we should use a kernel environment variable passed in > > from loader, since kern_envp is available *real early*, from the very > > beginning of init386(), which is called form locore just after going > > virtual. It needs a couple of tweaks to get this to work, and in > > particular, the environment variable will have to override the VM86 > > calls. > > It shouldn't "override it", rather it should simply lower the current > 4GB cap to whatever it's set to. This allows the BIOS sensing code to > correctly walk around holes, etc. Also, bear in mind the fun we had with BIOS reporting 15MB of ram and the like.. Capping is fine, so long as there's some way of forcing it to a given value if needed. Never assume BIOS writers are *always* competent. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message