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

Message-ID: <86802c440808260943k210be3edp54aebc9fea5366f5@mail.gmail.com>
Date:	Tue, 26 Aug 2008 09:43:44 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Helge Hafting" <helge.hafting@...el.hist.no>
Cc:	"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 Tue, Aug 26, 2008 at 2:32 AM, Helge Hafting
<helge.hafting@...el.hist.no> wrote:
> Yinghai Lu wrote:
>
>> please use "mtrr_spare_reg_nr=3 debug"
>>
>> you missed _nr.
>>
> Sorry. I got it right this time, and mtrr setup succeeded:
>
..
> $ cat /proc/mtrr
> reg00: base=0x00000000 (   0MB), size=1024MB: write-back, count=1
> reg01: base=0x40000000 (1024MB), size= 512MB: write-back, count=1
> reg02: base=0x60000000 (1536MB), size= 256MB: write-back, count=1
> reg03: base=0x70000000 (1792MB), size= 256MB: write-back, count=1
> reg04: base=0x7ff00000 (2047MB), size=   1MB: uncachable, count=1
> reg05: base=0xf3c00000 (3900MB), size=   2MB: write-combining, count=1
> reg06: base=0xf3800000 (3896MB), size=   4MB: write-combining, count=1
> reg07: base=0xf3000000 (3888MB), size=   8MB: write-combining, count=1
>
> This time X got its 3 regions, and no sluggishness when moving
> opaque windows. :-)

good.

>
> I hope this helps so the extra bootup parameters can be avoided in the
> release kernel.

that is a little bit hard.

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/