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]

Date:	Sun, 5 Apr 2009 15:41:09 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Meelis Roos <mroos@...ux.ee>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: strange MTRR on 2.6.29-git


* Meelis Roos <mroos@...ux.ee> wrote:

> > > 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
> 
> > that is original setting by BIOS.
> > it should be ok.
> > if you like, could try to enable
> > 
> > CONFIG_MTRR=y
> > CONFIG_MTRR_SANITIZER=y
> > CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
> > CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
> > 
> > it could do the clean up for you.
> 
> Thank you, it did clean it up:
> 
> reg00: base=0x000000000 (    0MB), size=  512MB, count=1: write-back
> reg01: base=0x0f2000000 ( 3872MB), size=   32MB, count=2: write-combining
> reg02: base=0x0f8000000 ( 3968MB), size=   64MB, count=1: write-combining
> 
> and it removed the overlapping MTRR-s altogether since there was 
> no RAM described t be here. Seems to work fine.
 
ok, great.

I'm wondering whether CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT should be 
1 by default in the future.

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