linux-kernel - Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?

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.64.0706050918160.16952@p34.internal.lan>
Date:	Tue, 5 Jun 2007 09:18:58 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Andi Kleen <andi@...stfloor.org>
cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't
 the kernel realize the BIOS has problems and re-map appropriately?

On Tue, 5 Jun 2007, Andi Kleen wrote:

>> So the only safe thing we can do is not use memory that is not
>> write-back cached.  That we can positively detect and is a
>> conservative action so if anything will work that will.
>
> Jesse wrote such a patch (or rather it limitted end_pfn), but it broke
> the X server for so far unknown reasons.
>
> -Andi
>

So the best solution is for a patch/function that calculates the E820 
memory map subtracts the non-cached memory and does the equivilant of 
append= in LILO config with the proper amount of memory?

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