From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756015AbZDENlq (ORCPT ); Sun, 5 Apr 2009 09:41:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752756AbZDENlg (ORCPT ); Sun, 5 Apr 2009 09:41:36 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:38728 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752365AbZDENlf (ORCPT ); Sun, 5 Apr 2009 09:41:35 -0400 Date: Sun, 5 Apr 2009 15:41:09 +0200 From: Ingo Molnar To: Meelis Roos , "H. Peter Anvin" , Thomas Gleixner Cc: Yinghai Lu , Linux Kernel list Subject: Re: strange MTRR on 2.6.29-git Message-ID: <20090405134109.GA24782@elte.hu> References: <86802c440904011143i65d99bd8x7a296f616f6bfccc@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Meelis Roos 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