From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Andi Kleen <andi@firstfloor.org>
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
Date: Tue, 5 Jun 2007 10:20:37 -0700
User-Agent: KMail/1.9.6
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
       Yinghai Lu <yhlu.kernel@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Justin Piszcz <jpiszcz@lucidpixels.com>, linux-kernel@vger.kernel.org
References: <Pine.LNX.4.64.0706011410130.3716@p34.internal.lan> <m1ejkrw576.fsf@ebiederm.dsl.xmission.com> <20070605094623.GA23274@one.firstfloor.org>
In-Reply-To: <20070605094623.GA23274@one.firstfloor.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706051020.37812.jbarnes@virtuousgeek.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 699
Lines: 17

On Tuesday, June 5, 2007 2:46 am Andi Kleen wrote:
> > So the only safe thing we can do is not use memory that is not
> > write-back cached.  That we can positively detect and is a
> > conservative action so if anything will work that will.
>
> Jesse wrote such a patch (or rather it limitted end_pfn), but it
> broke the X server for so far unknown reasons.

It looks like I broke the /proc/mtrr interface somehow... I'll try to 
fix it tomorrow.

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