linux-kernel - Re: 4Gb ram not showing up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0706070857500.1547@yvahk01.tjqt.qr>
Date:	Thu, 7 Jun 2007 08:58:40 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Satyam Sharma <satyam.sharma@...il.com>
cc:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Tom Moore <tmoore@...tial.ca>, linux-kernel@...r.kernel.org
Subject: Re: 4Gb ram not showing up


On Jun 7 2007 02:48, Satyam Sharma wrote:
> On 6/6/07, Lennart Sorensen <lsorense@...lub.uwaterloo.ca> wrote:
>> [...]
>> A better description would be:
>> 
>> "Select this if you have a 32-bit processor and memory mapped in the 1GB
>> to 4GB address range."
>> [...]
>> That one would be better as:
>> 
>> "Select this if you have a 32-bit processor and ram mapped in the address
>> range above 4GB."
>
> Ugh, no! How can we expect the user compiling a kernel to be *so*
> familiar with address space re-mapping / BIOSen (_his_ particular
> BIOS, specifically, and what / how it re-maps memory) / etc to be
> able to answer such questions? "Select ... if you have ... RAM
> installed" is perfectly clear, simple, and all that's needed.

Then explain it.

"Select this if you have a 32 bit cpu and ram mapped above 4 G.
To see where RAM is mapped, interpret the E820 lines from dmesg,
for more information see Documentation/e820.txt"

or something like that.


	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/