linux-kernel - Re: strange MTRR on 2.6.29-git

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.SOC.4.64.0904011722350.14173@math.ut.ee>
Date:	Wed, 1 Apr 2009 17:25:40 +0300 (EEST)
From:	Meelis Roos <mroos@...ux.ee>
To:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: strange MTRR on 2.6.29-git

> Found this on todays 2.6.29 + git. The same address range has both WB 
> and UC MTRR-s.
> 
> reg00: base=0x000000000 (    0MB), size=  512MB, count=1: write-back
> reg01: base=0x020000000 (  512MB), size=    1MB, count=1: write-back
> reg02: base=0x020000000 (  512MB), size=    1MB, count=1: uncachable
> reg03: base=0x0f2000000 ( 3872MB), size=   32MB, count=2: write-combining
> reg04: base=0x0f8000000 ( 3968MB), size=   64MB, count=1: write-combining

Actually, these double MTRR-s for the range @ 512M are there long time. 
Testbooted 2.6.20 that is the earliest kernel I have around here and 
this conflicting double MTRR is still there, so it's not a recent 
change. In 2.6.20 reg04 was not present but that's probably unimportant 
since reg01 and reg02 are the same.

-- 
Meelis Roos (mroos@...ux.ee)
--
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/