From owner-cvs-src@FreeBSD.ORG Mon Feb 28 21:59:50 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72C7E16A4CE; Mon, 28 Feb 2005 21:59:50 +0000 (GMT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECFED43D39; Mon, 28 Feb 2005 21:59:49 +0000 (GMT) (envelope-from wes@softweyr.com) Received: from salty (apollo2-12.stbernard.com [199.245.188.12]) by smtp-relay.omnis.com (Postfix) with ESMTP id 845E7881BCF; Mon, 28 Feb 2005 13:59:43 -0800 (PST) From: Wes Peters Organization: Softweyr.com To: Wes Peters Date: Mon, 28 Feb 2005 13:59:42 -0800 User-Agent: KMail/1.7.1 References: <200502282142.j1SLgvhh067909@repoman.freebsd.org> In-Reply-To: <200502282142.j1SLgvhh067909@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502281359.42589.wes@softweyr.com> cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 machdep.c src/sys/kern kern_mib.c src/sys/sys sysctl.h systm.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 21:59:50 -0000 On Monday 28 February 2005 01:42 pm, Wes Peters wrote: > wes 2005-02-28 21:42:57 UTC > > FreeBSD src repository > > Modified files: > sys/i386/i386 machdep.c > sys/kern kern_mib.c > sys/sys sysctl.h systm.h > Log: > Add a sysctl that records the amount of physical memory in the machine. In case you're wondering why anyone would want this, vs. the already existing hw.physmem, consider: hw.physmem: 526737408 hw.usermem: 509272064 hw.realmem: 535691264 The difference between 'realmem' and 'physmem' should always be the same for a given device, unless BIOS settings have altered the memory map somehow. We use this as a quick check to verify the BIOS settings haven't been altered (at least enough to change the memory map). You'd be astonished how much the physmem setting can bounce around on supposedly identical hardware. -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com