Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755847AbYJBWdh (ORCPT ); Thu, 2 Oct 2008 18:33:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753271AbYJBWdN (ORCPT ); Thu, 2 Oct 2008 18:33:13 -0400 Received: from rv-out-0506.google.com ([209.85.198.228]:16675 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753235AbYJBWdL convert rfc822-to-8bit (ORCPT ); Thu, 2 Oct 2008 18:33:11 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=CnK60EhtPWeMSiCEc3AYzJCIL0bALd4UxFQVmU1sKM+A7d7xTgu+L66+ULR/E9j0gT oQz1yNnUeDFyP0oxHkujBtCZKCIs4LAfblFdX5ShDxSRFsL3SQQRqsMRAfcolYeTqnNG 4tjL/QBO+Pc97VaI2sEiTmZWjo8zwXK6ewles= Message-ID: <86802c440810021533v572975e8n40e55009cc2b2d8a@mail.gmail.com> Date: Thu, 2 Oct 2008 15:33:10 -0700 From: "Yinghai Lu" To: "=?ISO-8859-1?Q?J.A._Magall=F3n?=" Subject: Re: [PATCH 2/2] x86: mtrr_cleanup try gran_size to less than 1M Cc: Linux-Kernel In-Reply-To: <20081003000314.771b2f68@werewolf.home> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-Disposition: inline References: <1222739652-17169-1-git-send-email-yhlu.kernel@gmail.com> <1222739652-17169-2-git-send-email-yhlu.kernel@gmail.com> <20081003000314.771b2f68@werewolf.home> X-Google-Sender-Auth: 79dedbe53a35b397 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1625 Lines: 42 On Thu, Oct 2, 2008 at 3:03 PM, J.A. Magall?n wrote: > On Mon, 29 Sep 2008 18:54:12 -0700, Yinghai Lu wrote: > >> >> so start from 64k instead of 1M >> > > Or there is something I don't catch about mtrrs, or it still does silly > things. > > I have an ASUS PCDL, dual xeon, 2Gb of memory. Mtrrs after cleanup are: > > werewolf:/proc> cat 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= 128MB: write-back, count=1 > reg04: base=0x78000000 (1920MB), size= 64MB: write-back, count=1 > reg05: base=0x7c000000 (1984MB), size= 64MB: write-back, count=1 > reg06: base=0x7ff00000 (2047MB), size= 1MB: uncachable, count=1 > > So it adds a last WB zone, but substracts the last 1Mb. (Why do > I have that stupid uncacheable mb ? probably a bios issue...) > But those two 64 mb zones could be add to a 128Mb, that new one > with previous to 256Mb and so on, giving something like: > > reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 > reg01: base=0x7ff00000 (2047MB), size= 1MB: uncachable, count=1 > > Is this incorrect ? > can you boot with mtrr_cleanup_debug? also what is /proc/mtrr with disable_mtrr_cleanup? YH -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/