linux-kernel - Re: 2.6.27 mtrr fixes do not work when X starts

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] [day] [month] [year] [list]

Date:	Wed, 27 Aug 2008 15:03:18 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Helge Hafting <helge.hafting@...el.hist.no>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Alexander Huemer <alexander.huemer@....ac.at>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: 2.6.27 mtrr fixes do not work when X starts

On Wed, Aug 27, 2008 at 02:53:25PM +0200, Helge Hafting wrote:
> Yinghai Lu wrote:
> >On Tue, Aug 26, 2008 at 2:32 AM, Helge Hafting
> ><helge.hafting@...el.hist.no> wrote:
> 
> >>I hope this helps so the extra bootup parameters can be avoided in the
> >>release kernel.
> >
> >that is a little bit hard.
> 
> Well, perhaps not 2.6.27, but I hope I won't need
> "mtrr_spare_reg_nr=3" forever. Or is my machine a strange
> corner case as far as mtrr's are concerned?

It's just a side effect of having far too much BIOS code 
in the kernel. These basic MTRRs should be set up by the BIOS and when
the kernel starts to think it knows better it ultimatively ends up
being far more platform dependent than it should be.

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