From owner-freebsd-hackers Thu Jul 1 15:19: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6BC5314A09 for ; Thu, 1 Jul 1999 15:19:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01520; Thu, 1 Jul 1999 15:14:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907012214.PAA01520@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Andrew Gallatin , hackers@freebsd.org Subject: Re: npx0 to set maxmem broken in -current? In-reply-to: Your message of "Fri, 02 Jul 1999 02:14:49 +0800." <19990701181449.846AA8A@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 15:14:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message