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: <86802c440706041759q1b2d528ex24b3de514d09d9ef@mail.gmail.com>
Date:	Mon, 4 Jun 2007 17:59:59 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Justin Piszcz" <jpiszcz@...idpixels.com>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Andi Kleen" <andi@...stfloor.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 6/4/07, Eric W. Biederman <ebiederm@...ssion.com> wrote:
>
> Exactly, and given that this is a fairly easy thing to do, and that
> occasionally we see systems where this happens (even if their BIOS is
> later fixed).  It is likely worth it for someone to write up the patch
> and that compare MTRRs with available memory, and to complain and
> reserve all memory that MTRRs claim is not write-back.
>
that is good.
Sometime BIOS can not even keep mtrr to the identical between
different CPU in SMP system.

Or reset mtrr according to e820 table.

YH
-
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/