linux-kernel - Re: memory beyond4GB invisible to the system even though CONFIG

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]

Date:	Wed, 14 Jan 2009 08:14:35 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	"Yinghai Lu" <yinghai@...nel.org>
Cc:	"James Kirin" <james.kirin40@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y

 > please do
 > 1. boot linux with "disable_mtrr_trim" in grub.conf etc
 > 2. after booting input:
 > echo "base=0x100000000 size=0x20000000 type=write-back" >/proc/mtrr

Is there any way we can have the kernel do this automatically if there
are any free mtrr slots?  I would guess this type of BIOS bug is pretty
common (desktop boards not validated with > 4GB of RAM), and having the
kernel throw away 4GB of memory unless the user does some fancy
scripting is not very friendly (not to mention the fact that things are
likely to be very slow until the mtrr fixup script runs).

 - R.
--
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/