Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Feb 2005 15:19:35 -0700
From:      Scott Long <scottl@samsco.org>
To:        Wes Peters <wes@softweyr.com>
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
Message-ID:  <422398F7.6010004@samsco.org>
In-Reply-To: <200502281359.42589.wes@softweyr.com>
References:  <200502282142.j1SLgvhh067909@repoman.freebsd.org> <200502281359.42589.wes@softweyr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Wes Peters wrote:
> 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.
> 

So how does this interact with the PCI memory hole at the upper end of 
the 4GB boundary?

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?422398F7.6010004>